OXLOADER
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.
Techniques & procedures
14 distinct techniques documented for this family, organized by ATT&CK tactic.
Resource Development
2 techniques
Resource Development
Initial Access
1 technique
Initial Access
Execution
2 techniques
Execution
Privilege Escalation
2 techniques
Privilege Escalation
Stealth
6 techniques
Stealth
The loader uses several obfuscation layers (control-flow flattening, opaque predicates, mixed Boolean-Arithmetic), self-modifying decryption stubs, and abuses the Windows .reloc section to stage shellcode
A second variant of OXLOADER was also discovered on May 13, 2026, this time masquerading as a Node.js installer binary rather than API Monitor.
and unpacks itself in memory using self-modifying decryption routines.
while also taking steps to ensure it's not run on sandboxed environments
Discovery
2 techniques
Discovery
Command and Control
1 technique
Command and Control
Users who end up interacting with the site are served a batch script hosted on Storj... Running the batch script displays a bogus installation wizard user interface (UI), while stealthily downloading a next-stage payload, a Storj-hosted executable dubbed OXLOADER through a PowerShell command
IOCs tracked for this family
19 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.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Previously unreported malware loader used to deliver CastleStealer. It uses multiple obfuscation layers, self-modifying decryption stubs, abuses the Windows .reloc section to stage shellcode, employs DLL side-loading, and includes anti-VM/sandbox evasion techniques.
A newly documented malware loader delivered via fake Google Ads and counterfeit Node.js installer pages. It uses anti-sandbox and anti-VM checks, obfuscation, code hidden in the .reloc section, and in-memory unpacking to evade analysis before delivering the final payload.
Previously undocumented Windows loader distributed via malicious Google Ads impersonating Node.js. It uses heavy obfuscation, self-modifying decryption stubs, anti-sandbox and geographic/language exclusion checks, abuses the .reloc section to stage shellcode, copies dui70.dll to a temporary .ocx file, and ultimately delivers CASTLESTEALER in memory via DonutLoader.
The version that knows your environment.
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.