← Back to feed

800+ Malicious npm Packages: AI-Slop Typosquatting Campaign Distributes Cross-Platform RAT

Date: 2026-08-17
Tags: supply-chain, malware

Executive Summary

Nearly 800 malicious npm packages using AI-generated ("slop") or randomly generated typosquatting names deliver a powerful cross-platform RAT and infostealer payload, with updates on August 11, 2026. The campaign targets developers across Linux, macOS, and Windows platforms.

Campaign Summary

FieldDetail
Campaign / MalwareAI-Slop Typosquatting Campaign (800+ packages)
AttributionUnknown (confidence: low)
Targetnpm developers; cross-platform users
VectorTyposquatted package names; install-time execution via postinstall scripts
Statusactive
First Observed2026-08-11

Detailed Findings

Packages appear to use AI slop squatted, or randomly generated typo-squatting package names, but all deliver a powerful RAT and infostealer payload. The scale and coordination suggest automated package generation and publishing, consistent with malware-as-a-service infrastructure.

MITRE ATT&CK Mapping

TechniqueIDContext
Typosquatting / Dependency ConfusionT1195.003Malicious packages registered with names similar to legitimate npm packages
Execution via Package ManagerT1059.001Postinstall scripts execute malware on npm install
Information GatheringT1592RAT and infostealer exfiltrate developer credentials and system data

IOCs

Domains

_No specific package IOCs published; OpenSourceMalware researcher Paul McCarty and The Hacker News published updates on August 11, 2026. Recommend checking npm security advisories and malware tracking databases for package names._

Full URL Paths

_No specific package IOCs published; OpenSourceMalware researcher Paul McCarty and The Hacker News published updates on August 11, 2026. Recommend checking npm security advisories and malware tracking databases for package names._

Splunk Format

_No IOCs available for Splunk query_

Affected Platforms

npm
Linux
macOS
Windows

Detection Recommendations

Monitor npm package registrations for unusual patterns of similarly-named packages or AI-generated names with common typosquatting targets (ollama, langchain, openai, anthropic, vercel). Implement npm postinstall script sandboxing and prohibit lifecycle script execution for unvetted packages. Use npm audit and third-party supply chain scanners (Snyk, Sonatype) to detect typosquatted dependencies. Monitor for sudden spikes in package installation from new or low-reputation publishers. Implement strict lockfile pinning and registry authentication. Alert on any postinstall execution that attempts credential harvesting or network exfiltration.

References