Researchers tied the SandCat hacking group to Uzbekistan’s State Security Service after a series of operational security failures exposed the actor’s infrastructure, malware development environment, and exploit activity. Kaspersky said it first identified the group after finding Chainshot malware and a zero-day exploit on a victim machine in the Middle East, then traced additional infrastructure and three more zero-days linked to the same operator. The investigation connected SandCat to Uzbekistan through infrastructure associated with the itt.uz domain, registration data referencing Military Unit 02616 in Tashkent, and network proximity between suspected development systems and state security email infrastructure.
Separate reporting documented phishing and web attacks targeting Uzbek human rights activists and independent media, aligning the broader campaign with domestic surveillance and repression objectives. Kaspersky said SandCat’s mistakes included using security software with telemetry enabled on development machines, uploading malware from operational IP addresses to VirusTotal, and leaving a screenshot of its in-development Sharpa platform inside a malicious test file. Those errors exposed tooling, infrastructure, and the apparent use of multiple purchased zero-day exploits, while also revealing overlap with exploit activity previously attributed to operators linked to Saudi Arabia and the United Arab Emirates.

TTPs, infrastructure, and targeting history in one profile.
7 events from the most recent confirmed update back to the earliest known activity.
In October 2018, SandCat began developing its own attack platform, called Sharpa. Kaspersky later gained visibility into the platform through a screenshot embedded in a malicious Word test file.
In October 2018, Kaspersky discovered Chainshot malware on a victim machine in the Middle East and determined it had been installed using a zero-day exploit. This investigation became the starting point for uncovering the SandCat threat actor.
The article states that Uzbekistan's State Security Service appeared in Hacking Team emails leaked by Phineas Fisher in 2015. Those leaked records were later referenced alongside Kaspersky's SandCat findings.
According to Hacking Team emails leaked by Phineas Fisher, Uzbekistan's State Security Service spent nearly one million dollars on Hacking Team tools during the 2011 to 2015 period. The article cites this as earlier evidence of the service's surveillance procurement activity.
Registration information cited by Kaspersky showed the itt.uz domain was registered in 2008 to Military Unit 02616 in Tashkent, Uzbekistan. Kaspersky later used this infrastructure link as part of its attribution of SandCat to Uzbekistan's State Security Service.
Kaspersky researcher Brian Bartholomew presented the company's findings about SandCat at the VirusBulletin conference in London. The presentation described the group's operational security failures, exposed infrastructure, and burned zero-days.
Kaspersky researchers identified a threat actor they named SandCat and assessed it to be linked to Uzbekistan's State Security Service. Their investigation also uncovered three additional zero-day exploits used by the same group and tied its infrastructure to itt.uz and nearby SSS-linked IP space.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See this adversary's TTPs, infrastructure, and targeting history, correlated against your exposure.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.