Skip to main content
Mallory
Back to malware
MalwareUsed by 3 actorsExploits 1 CVE

BLINDINGCAN

BLINDINGCAN is a Lazarus-linked remote access trojan (RAT) / backdoor associated with North Korean activity. The provided content attributes its use to Lazarus Group and broader DPRK operations, including financially motivated and espionage activity, with targeting noted against finance, cryptocurrency, defense, healthcare, and nonprofit organizations. It is also referenced in CISA detection content as a Hidden Cobra RAT family.

Observed delivery and execution tradecraft includes phishing emails containing malicious Microsoft Office documents and lures that trick victims into enabling or executing malicious macros. The malware has been described as a final payload in Lazarus intrusion chains, including a newer variant with additional cryptographic elements and expanded capabilities. The content also states Lazarus used a bring-your-own-vulnerable-driver (BYOVD) technique to deploy BLINDINGCAN.

Reported capabilities and behaviors include sending user and system information to command-and-control infrastructure via HTTP POST, encoding C2 traffic with Base64, loading and executing DLLs in memory at runtime, modifying file and directory timestamps for anti-forensics, and hiding payloads behind legitimate-looking filenames such as "iconcache.db." The malware has also been signed with code-signing certificates, including certificates such as CodeRipper, to aid evasion.

The content further notes that BLINDINGCAN has been used alongside other Lazarus tooling in recent Medusa ransomware-related intrusions, including Comebacker, ChromeStealer, InfoHook, Mimikatz, Curl, and RP_Proxy. It is also described as a predecessor to the Lazarus LightlessCan backdoor, characterized in the content as a flagship HTTP(S) Lazarus RAT.

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.

EXPLOITED CVES

Vulnerabilities exploited

1 CVE Mallory has correlated with this family across public research and vendor advisories. Each row links to the full Mallory page for that vulnerability.

1 CVES
CVE-2022-0609Use-after-free RCE in Google Chrome Animation

Lazarus’ Bring Your Own Vulnerable Driver (BYOVD) technique to deploy BLINDINGCAN

via sekoia blogblog.sekoia.io
THREAT ACTORS

Groups observed using it

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

View more details
Lazarus

The profile shows: Attributed to: North Korea Motivations: Financial gain, Espionage Targets: Finance, Cryptocurrency, Defense Malware used: WannaCry, Hermes, BLINDINGCAN (all auto-linked by MITRE connector)

via infosec writeupsinfosecwriteups.com
APT38

Malware and Tools · Blindingcan : A remote access Trojan associated with Lazarus

via ahnlab asec blogasec.ahnlab.com
Andariel

"Tools Used In Recent Campaigns... Blindingcan remote access Trojan"

via infosecurity magazine cominfosecurity-magazine.com
MITRE ATT&CK

Techniques & procedures

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

Resource Development

1 technique
T1584.004ServerEvidence1

“Compromised servers were used by the Lazarus HTTP(S) backdoors and the downloader for C&C.”

Initial Access

1 technique
T1566.001Spearphishing AttachmentEvidence2

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

5 techniques
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.007JavaScriptEvidence1

The content repeatedly mentions malicious macros in Word/Excel documents, such as "enable macros," "embedded macros," and "macro-enabled documents."

T1129Shared ModulesEvidence1

Astaroth uses the LoadLibraryExW() function to load additional modules. Attor's dispatcher can execute additional plugins by loading the respective DLLs. ... LightSpy's main executable and module .dylib binaries are loaded using ... dlopen() ... dlsym() ... RotaJakiro uses ... .so files ... using dlopen() and dlsym().

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.002Malicious FileEvidence1

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.

Privilege Escalation

1 technique
T1068Exploitation for Privilege EscalationEvidence1

Of particular interest and documented as a first seen in the wild in 2022 (although leveraged at least since October 2021 as part of Operation DreamJob), Lazarus’ Bring Your Own Vulnerable Driver (BYOVD) technique to deploy BLINDINGCAN.

Stealth

7 techniques
T1027Obfuscated Files or InformationEvidence4

The content repeatedly describes payloads, strings, configuration files, scripts, URLs, and binaries being obfuscated or encoded using Base64, XOR, RC4, AES, RSA, hex encoding, custom algorithms, and other methods across many malware families and threat actors.

T1027.002Software PackingEvidence1

"Sandworm Team used UPX to pack a copy of Mimikatz"; "APT38 has used several code packing methods such as Themida, Enigma, VMProtect, and Obsidium"; "Lazarus Group packed malicious .db files with Themida to evade detection."

T1036MasqueradingEvidence2

During the 2016 Ukraine Electric Power Attack, DLLs and EXEs with filenames associated with common electric power sector protocols were used to masquerade files.

T1070Indicator RemovalEvidence2

Examples throughout the content include deleting tools, logs, malware-related files, staged archives, screenshots, temporary files, and exfiltrated data 'to cover their tracks,' 'reduce their footprint,' 'remove traces of activity,' or as part of 'post-intrusion cleanup.'

T1070.004File DeletionEvidence5

The content repeatedly describes threat actors and malware deleting files, tools, scripts, logs, droppers, staged data, and artifacts from compromised systems to cover tracks, remove evidence, or self-delete.

T1070.006TimestompEvidence1

APT28 has performed timestomping on victim files. APT29 has used timestomping to alter the Standard Information timestamps on their web shells to match other files in the same directory. APT32 has used scheduled task raw XML with a backdated timestamp... APT38 has modified data timestamps to mimic files that are in the same folder on a compromised host.

T1140Deobfuscate/Decode Files or InformationEvidence5

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.

Defense Impairment

1 technique
T1553.002Code SigningEvidence1

The content repeatedly describes threat actors and malware using valid, stolen, forged, self-signed, or abused code-signing certificates to sign malware and appear legitimate, including examples such as AppleJeus using a valid digital signature from Sectigo, APT41 leveraging code-signing certificates, FIN7 signing Carbanak payloads, and SUNBURST being digitally signed by SolarWinds.

Discovery

3 techniques
T1016System Network Configuration DiscoveryEvidence3

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.

T1082System Information DiscoveryEvidence3

The content repeatedly describes malware and threat actors collecting host details such as OS version, hostname, architecture, CPU, memory, BIOS, domain, language, and other configuration data; e.g., "APT41 uses multiple built-in commands such as systeminfo and net config Workstation to enumerate victim system basic configuration information."

T1083File and Directory DiscoveryEvidence3

The content repeatedly describes malware and threat actors listing files and directories, enumerating drives, searching for files by extension/name/path, retrieving file metadata, and browsing file systems (for example: "APT28 has used Forfiles to locate PDF, Excel, and Word documents during collection" and "cmd can be used to find files and directories with native functionality such as dir commands").

Command and Control

2 techniques
T1071.001Web ProtocolsEvidence4

The content repeatedly describes threat actors and malware using HTTP and HTTPS for command and control, such as: "Sandworm Team used BlackEnergy to communicate between compromised hosts and their command-and-control servers via HTTP post requests."

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.

Exfiltration

1 technique
T1041Exfiltration Over C2 ChannelEvidence4

Many entries state malware or actors can upload, transfer, send, or exfiltrate files from compromised hosts to command-and-control servers or attacker infrastructure.

INDICATORS OF COMPROMISE

IOCs tracked for this family

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

View more in app
Network
7 tracked

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

Hashes
13 tracked

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

Other
6 tracked

Other indicator types observed in public reporting.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app3 months ago
ip.v4●●●●●●●●●●●●View more in app4 months ago
hash.sha256●●●●●●●●●●●●View more in app8 months ago
ip.v4●●●●●●●●●●●●View more in app8 months ago
uri●●●●●●●●●●●●View more in app8 months ago
uri●●●●●●●●●●●●View more in app8 months 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 matching26

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

Threat actor attribution3

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

Exploited vulnerabilities1

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 mapping22

Every documented technique, ranked by evidence weight.

Researcher chatter

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