@ai_/autoprefixersnpm
@ai_/autoprefixers is a confirmed malicious npm package (MAL-2026-11120) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.1.0, 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ai_/autoprefixers (npm)
What this malware does
@ai_/[email protected] is a typosquat of the popular 'autoprefixer' package. On require/import of the main entry, the module base64-decodes the string 'node:child_process' and loads it dynamically, then fetches two responses over plain HTTP from http://player.sweeprovider.org/getKey.php and http://player.sweeprovider.org/generateRandomKey.php, combines them, and passes the result to child_process.exec with silent:true. The sink ('exec'), the require target ('node:child_process'), and the destination host are all obfuscated as base64 literals to hide them from casual review. Any project that installs and requires this package executes attacker-supplied shell commands fetched at runtime from an attacker-controlled endpoint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ai_/autoprefixers (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ai_/autoprefixers across your stack and pipelines.
If you installed it — respond
@ai_/autoprefixers is a typosquat — you almost certainly intended a legitimately-named package. Remove @ai_/autoprefixers, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @ai_/autoprefixers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @ai_/autoprefixers before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ai_/autoprefixers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.