Dark Web Profile: Berserk Bear
Berserk Bear is a Russian state-sponsored cyber espionage group linked to the FSB. They have been active since at least 2010 under many names (Dragonfly, Energetic Bear, Havex, Crouching Yeti, Koala, TeamSpy, etc.) and specialize in penetrating critical infrastructure.
Who Is Berserk Bear?
Berserk Bear’s earliest known activity traces back to the TeamSpy campaign, uncovered in 2013 by CrySyS Lab after a warning from the Hungarian National Security Authority. Investigators found command-and-control servers and malware samples that had been in use since 2010.
The attackers misused the TeamViewer remote access tool to gain control of infected machines, allowing them to collect data from both everyday users and high-value targets. Victims included industrial firms, research bodies, and diplomatic organizations, showing that the operation aimed at long-term espionage rather than quick profit. What started as TeamSpy was later recognized as the foundation of the group now tracked as Berserk Bear.
Threat actor card for Berserk Bear
Berserk Bear is an FSB-linked hacking unit and should not be confused with GRU teams like Sandworm (Unit 74455), which specialize in disruptive operations. Instead, Berserk Bear focuses on espionage aligned with the FSB’s broader cyber mission.
The FSB reportedly runs two main centers: the 16th Center (which handles signals intelligence and foreign cyber targeting) and the 18th Center (which oversees domestic security but also operates abroad). Berserk Bear, part of Center 16, is tasked with penetrating critical infrastructure, especially in the energy sector, through reconnaissance and surveillance. This structure and mission are detailed in the Russian Cyber Units report by the Congressional Research Service.
Over more than a decade of activity, Berserk Bear has adapted its tactics and focus while keeping a consistent mission, gaining deep, long-term access to critical systems for intelligence collection.
Their earliest operation, TeamSpy (2010-2013), misused TeamViewer for remote surveillance of industrial, diplomatic, and research targets. Later campaigns like Dragonfly (2013-2014) and Dragonfly 2.0 (2015-2017) expanded into U.S. and European energy systems, while 2020 onward saw intrusions into state, local, and aviation networks. The U.S. DOJ’s 2022 indictment formally tied the group to the FSB. Most recently, in 2025, Cisco Talos and the FBI linked Berserk Bear to the Static Tundra campaign, exploiting old Cisco router vulnerabilities to infiltrate telecom and education networks.
Key milestones from Berserk Bear’s 2010 to 2025
What Are Berserk Bear’s Targets?
Berserk Bear’s primary focus lies in penetrating critical infrastructure, particularly in the Energy and Utility sectors. They often seek access to industrial control systems (ICS) and operational technology networks to map systems, steal design documents, and collect credentials. Over time, their reach has expanded: they also target government agencies, municipal networks, aviation systems, telecommunications infrastructure, and academic and research institutions.
For instance, during the Dragonfly / Havex campaigns they compromised energy and pipeline companies across Europe and North America. More recently, they infiltrated U.S. state, local, tribal, and territorial (SLTT) networks, including those connected to aviation systems. In 2025 they exploited a known Cisco router vulnerability (CVE-2018-0171) to gain long-term access to routers and switches across telecom, education, and infrastructure networks.
SOCRadar-Cyber Threat Intelligence -> Vulnerability Intelligence
How Does Berserk Bear Operate?
Berserk Bear runs patient, multi-stage espionage campaigns. The group moves in small steps. It focuses on staying hidden and collecting intelligence over long periods.
Initial Access
The group gains entry by phishing targeted individuals, by compromising websites engineers trust (watering-hole attacks), and by trojanizing legitimate vendor software in supply-chain attacks.
In early campaigns they used the Havex backdoor embedded in ICS vendor installers and used drive-by compromises of industry sites to deliver malware. Later they also exploited public-facing application flaws and weak remote services to get inside.
Execution
Once a user or host is compromised, Berserk Bear runs remote-access tools and custom RATs. They have abused legitimate remote admin software (TeamViewer) and deployed Havex/Oldrea and other tailored implants. They also run scripts and common system interpreters (PowerShell, Windows command shell, Python) to execute tasks without dropping noisy binaries. This lets them act quickly while lowering detection risk.
Persistence
The group establishes long-term access using multiple methods. They create or manipulate accounts and registry autorun entries. They install backdoors on hosts. In later campaigns they gained persistence on network devices by exploiting Cisco Smart Install (CVE-2018-0171) and by leveraging router implants (historic examples include SYNful Knock). Persisting on routers and switches gives them a stealthy foothold that survives OS reboots and endpoint cleans.
Privilege Escalation
Berserk Bear tries to capture NTLM hashes, force authentication to attacker servers, and dump local password stores. The group then reuses stolen credentials to access domain resources, elevate privileges, and reach OT systems. This credential-focused approach is a constant across their campaigns.
Discovery (Network and ICS/OT)
After they hold a foothold, they map the environment. They run network and file discovery scripts, enumerate domain accounts, and scan for vulnerable services. In energy-sector intrusions they ran ICS-specific probes, looking for OPC servers, PLCs, and other control devices, to map plant topology and identify control points. They also harvest router and switch configuration files to learn network paths and control points.
Lateral Movement and Pivoting
With credentials and network maps in hand, Berserk Bear moves laterally. They use remote services (RDP, PsExec) and pass-the-hash techniques to hop from corporate IT into engineering or OT segments. Compromised network devices often act as pivot points, letting the actors reach systems that standard endpoint tools can’t touch.
Collection and Exfiltration
The group collects engineering docs, system configs, email, and credentials. They stage data into archives and move it out via common protocols or covert channels. They may compress files before exfiltration and then use HTTP(S) or other blended channels to hide data transfers. Their goal is intelligence, not immediate financial gain.
C2 and Defense Evasion
Berserk Bear uses Command and Control (C2) channels that blend into normal traffic and hide in legitimate protocols. They reuse legitimate admin tools during operations to avoid dropping suspicious files. They also tamper with logs, clear events, and alter access controls to cover their tracks. Router-level compromise amplifies these evasion techniques by letting them modify network logging and ACLs at the infrastructure layer.
Berserk Bear’s attack chain summary
Why do routers and network gear matter to them?
Network devices hold an outsized value. They store configuration files, routing rules, device credentials, and topology. They also proxy traffic and connect IT to OT zones. By owning routers and switches, Berserk Bear gains broad visibility and durable persistence. Recent Static Tundra activity shows the group stealing device configs en masse and modifying settings to ensure continued stealthy access.
How to Defend Against Berserk Bear?
Berserk Bear relies on phishing, supply-chain tampering, and exploiting network gear. Defense starts with tightening entry points and watching for quiet, long-term intrusions.
Limit initial access
Use multi-factor authentication on email and remote access. Filter attachments and links in mail. Keep web servers patched and restrict exposure of admin panels.
Harden endpoints
Patch systems fast. Use necessary solutions like EDR to spot unusual scripting with PowerShell or cmd. Remove unnecessary admin rights and use allow-listing on sensitive hosts.
Protect credentials
Use MFA everywhere. Rotate and manage admin passwords through LAPS or similar tools. Watch for credential-dumping tools and suspicious NTLM or SMB activity.
Secure network devices
Patch and harden routers and switches. Disable unused services like Smart Install or SNMPv1/2. Isolate management interfaces and log configuration changes.
Plan for recovery
Back up configs and systems. Keep a tested incident-response plan ready to reset credentials and rebuild devices if needed.
How Can SOCRadar Help?
SOCRadar Supply Chain Intelligence (SCI) 2.0 gives full visibility into third-party risks that Berserk Bear often exploits. It unifies data from ASM, DRP, and CTI modules to track exposed vendors, vulnerable partners, and compromised supplier assets. With 125+ data-driven checks, it identifies weak links before attackers reach internal systems.
Beyond the supply chain, SOCRadar also strengthens overall defense by monitoring phishing domains, leaked credentials, and exploited vulnerabilities, helping organizations detect, prioritize, and respond to APT campaigns faster.
SOCRadar Supply Chain Intelligence (SCI) 2.0
MITRE ATT&CK TTPs of Berserk Bear
| ID | Name | Use |
| T1087.002 | Account Discovery: Domain Account | DragonFly/Berserk Bear batch scripts to enumerate domain users. |
| T1098.007 | Account Manipulation: Additional Local or Domain Groups | DragonFly/Berserk Bear added accounts to administrators groups. |
| T1583.001 | Acquire Infrastructure: Domains | They registered domains for targeting. |
| T1583.003 | Acquire Infrastructure: Virtual Private Server | They acquired VPS infrastructure. |
| T1595.002 | Active Scanning: Vulnerability Scanning | They scanned for Citrix and Exchange vulnerabilities. |
| T1071.002 | Application Layer Protocol: File Transfer Protocols | They used SMB for C2. |
| T1560 | Archive Collected Data | They compressed data into .zip files. |
| T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | They added a Registry Run key (ntdll) for persistence. |
| T1110 | Brute Force | They attempted credential brute force. |
| T1110.002 | Password Cracking | They ran Hydra and CrackMapExec. |
| T1059 | Command and Scripting Interpreter | They used command-line interpreters. |
| T1059.001 | PowerShell | They ran PowerShell scripts. |
| T1059.003 | Windows Command Shell | They used batch scripts. |
| T1059.006 | Python | They used Python and installed Python 2.7. |
| T1584.004 | Compromise Infrastructure: Server | They compromised websites to host C2 and modules. |
| T1136.001 | Create Account: Local Account | They created local and administrator accounts. |
| T1005 | Data from Local System | They collected local system data. |
| T1074.001 | Data Staged: Local Data Staging | They staged data in %AppData%out. |
| T1189 | Drive-by Compromise | They used strategic web compromise and a custom exploit kit. |
| T1114.002 | Email Collection: Remote Email Collection | They accessed email via Outlook Web Access. |
| T1190 | Exploit Public-Facing Application | They exploited Citrix, Exchange, and Fortinet CVEs. |
| T1203 | Exploitation for Client Execution | They exploited Adobe Flash CVE-2011-0611. |
| T1210 | Exploitation of Remote Services | They exploited Netlogon CVE-2020-1472. |
| T1133 | External Remote Services | They used VPNs and OWA for remote access. |
| T1083 | File and Directory Discovery | They used batch scripts to list files and folders. |
| T1187 | Forced Authentication | They harvested hashed credentials via SMB and modified .LNK icons. |
| T1591.002 | Gather Victim Org Information: Business Relationships | They collected OSINT on business relationships. |
| T1564.002 | Hide Artifacts: Hidden Users | They modified the Registry to hide accounts. |
| T1562.004 | Impair Defenses: Disable or Modify System Firewall | They disabled host firewalls and opened RDP port 3389. |
| T1070.001 | Indicator Removal: Clear Windows Event Logs | They cleared Windows and other logs. |
| T1070.004 | Indicator Removal: File Deletion | They deleted files and screenshots. |
| T1105 | Ingress Tool Transfer | They copied and installed tools on victims. |
| T1036.010 | Masquerading: Masquerade Account Name | They created accounts that looked like service or backup accounts. |
| T1112 | Modify Registry | They used Reg to change Registry settings. |
| T1135 | Network Share Discovery | They browsed file servers and viewed ICS/SCADA files. |
| T1588.002 | Obtain Capabilities: Tool | They used Mimikatz, CrackMapExec, and PsExec. |
| T1003.002 | OS Credential Dumping: Security Account Manager | They ran SecretsDump to dump SAM hashes. |
| T1003.003 | OS Credential Dumping: NTDS | They dumped NTDS and obtained ntds.dit. |
| T1003.004 | OS Credential Dumping: LSA Secrets | They dumped LSA secrets with SecretsDump. |
| T1069.002 | Permission Groups Discovery: Domain Groups | They enumerated domain admins and users via batch scripts. |
| T1566.001 | Phishing: Spearphishing Attachment | They sent emails with malicious attachments. |
| T1598.002 | Phishing for Information: Spearphishing Attachment | They used Office attachments to harvest credentials. |
| T1598.003 | Phishing for Information: Spearphishing Link | They used PDFs with links to credential-harvest sites. |
| T1012 | Query Registry | They queried the Registry for victim info. |
| T1021.001 | Remote Services: Remote Desktop Protocol | They moved laterally via RDP. |
| T1018 | Remote System Discovery | They obtained host lists in the environment. |
| T1053.005 | Scheduled Task/Job: Scheduled Task | They used scheduled tasks to log out accounts and run files. |
| T1113 | Screen Capture | They captured screens using scr.exe (ScreenUtil). |
| T1505.003 | Server Software Component: Web Shell | They installed web shells on public servers. |
| T1608.004 | Stage Capabilities: Drive-by Target | They compromised sites to host exploit kits. |
| T1195.002 | Supply Chain Compromise: Compromise Software Supply Chain | They trojanized vendor installers for control system software. |
| T1016 | System Network Configuration Discovery | They used batch scripts to enumerate trusts and zones. |
| T1033 | System Owner/User Discovery | They ran query user on victim hosts. |
| T1221 | Template Injection | They injected SMB URLs into Word attachments to force auth. |
| T1204.002 | User Execution: Malicious File | They used spearphishing to get users to open attachments. |
| T1078 | Valid Accounts | They used compromised valid credentials. |
| T0817 | Drive-by Compromise (ICS) | They used watering hole redirects to deliver Backdoor.Oldrea or Trojan.Karagany. |
| T0862 | Supply Chain Compromise (ICS) | They trojanized ICS vendor software packages. |
Source

