Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
The emergence of SmashJacker, a payload distinct from ChromeLoader but that also stemmed from Charcoal Stork initial access, led to our decision to continue tracking Charcoal Stork separately.
13 distinct techniques documented for this family, organized by ATT&CK tactic.
Analysis of SmashJacker and ChromeLoader MSI files delivered via concurrent Charcoal Stork campaigns showed several distinctions that led us to suspect Charcoal Stork is a pay-per-install (PPI) provider, responsible for the file naming and SEO and/or malvertising to get the click.
reg.xml is an xml formatted scheduled task that runs every 5 minutes and runs the persistence executable that created it.
Pulling that thread led us to an interesting pattern of files masquerading as cracked games and software or wallpaper downloads.
128 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
Other indicator types observed in public reporting.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A payload delivered by Charcoal Stork. Unlike ChromeLoader, it was not built with Advanced Installer and instead installs a trojanized version of 7zip, which installs a malicious browser extension.
Distinct payload delivered following Charcoal Stork initial access; no further functional detail is provided in the content.
A persistent malicious Chromium extension delivered via trojanized installers from piracy-themed sites. It hijacks browser searches, redirects users through actor-controlled affiliate infrastructure, generates ad revenue, collects victim analytics, and uses registry policy abuse, scheduled tasks, or AppInit DLLs for persistence while resisting removal.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.