Skip to content

Red Russians: How Russian APT Groups Follow Offensive Security Research

Will Thomas

How Russian state-sponsored APTs weaponize public red team tools and POCs within days of release.

Summary

Introduction: The Offensive Research Dilemma

Will Thomas, seasoned cyber threat intelligence researcher, presents a deep dive into how Russian state-sponsored advanced persistent threat (APT) groups actively track, adopt, and operationalize open-source offensive security research. While red team tools and public proof-of-concept (POC) exploits are created to help defenders validate and improve enterprise security controls, hostile intelligence services frequently repurpose these exact tools into active espionage campaigns—often within days or weeks of publication.

Russian Intelligence Services and APT Groups Profiled

Thomas maps out the landscape of Russian threat actors monitored in his research:

APT28 (Fancy Bear / Forest Blizzard): Associated with the Russian military intelligence agency (GRU Unit 26165), known for rapid exploit adoption and aggressive cyber-espionage.

APT29 (Cozy Bear / Midnight Blizzard): Attributed to the Russian Foreign Intelligence Service (SVR), recognized for sophisticated, stealthy tradecraft targeting cloud environments, Microsoft 365, and supply chains.

Sandworm (Seashell Blizzard / GRU Unit 74455): Notorious for disruptive cyber warfare, operational technology attacks, and data wiping campaigns.

Turla (Waterbug / Venomous Bear): Aligned with the FSB, known for specialized covert implants and complex multi-stage infection chains.

Rapid Weaponization of Public Exploits and Tools

Thomas illustrates how threat actors systematically scan security blogs, conference presentations, and GitHub repositories for weaponizable material. Rather than expending resources developing bespoke exploits from scratch, Russian APTs leverage community tooling to reduce operational costs and blend in with legitimate red team assessments.

Case Studies: TeamsPhisher, ClickFix, and TeamCity

The presentation highlights several real-world examples of rapid tool adoption:

TeamsPhisher: Within days of the open-source release of this Microsoft Teams phishing automation utility, Russian actors integrated the tool into live campaigns targeting government and defense entities.

ClickFix Social Engineering: When researchers documented a novel social engineering lure that tricked users into running clipboard-injected PowerShell commands via the Windows Run dialog (Win+R / Ctrl+V) under the guise of solving a CAPTCHA, APT28 deployed the technique against Ukrainian targets within weeks.

TeamCity Pre-Auth RCE: Public POCs for JetBrains TeamCity server vulnerabilities were weaponized almost immediately by Russian state actors to compromise software development infrastructure.

The Russian APT Tool Matrix

To help defenders catalog and detect these threats, Thomas introduced the "Russian APT Tool Matrix" on GitHub. The matrix classifies tools across core MITRE ATT&CK tactical categories:

Credential Theft: Ubiquitous use of Mimikatz, AADInternals, and token extraction tools.

Defense Evasion: Drivers and utilities like EDRSandBlast to blind endpoint protection agents.

C2 and Post-Exploitation: Widespread adoption of Cobalt Strike, Impacket, Sliver, and cracked underground releases of Brute Ratel C4.

Discovery and Exfiltration: Scripted cloud API tools abusing legitimate services (Microsoft Graph API, OneDrive, Google Drive) for covert data exfiltration.

Threat Hunting and Detection Engineering Workflows

Thomas details a collaborative workflow uniting CTI, threat hunting, and security engineering teams. CTI analysts collect emerging tool releases and extract structural artifacts; threat hunters write hunting queries; and detection engineers deploy and refine alerts in SIEM and EDR platforms. Threat hunters must proactively emulate newly published offensive tools rather than waiting months for formal threat intelligence reports.

Key Takeaways for Red and Blue Teams

Think Before Publishing: Offensive researchers and red teamers must weigh the defensive benefit against the operational risks before open-sourcing fully automated exploit tooling on GitHub.

Detect Common Tradecraft: Blue teams must prioritize robust detection engineering against widely shared post-exploitation tools, living-off-the-land techniques, and script block logging.

Proactive Emulation: Incorporate newly disclosed adversary TTPs into threat hunting cycles immediately to prevent nation-state dwell time.

Related talks

War Stories·48 min

Mikko Hypponen

Mikko Hypponen reflects on living 100 miles from Russia, tracing the evolution of Russian state cyber programs, patriotic hacker collectives, and NATO integration.

threat-intelligencerussiageopolitics+2