Which versions of @ai_/autoprefixers are malicious?

The following npm versions of @ai_/autoprefixers are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate @ai_/autoprefixers if I installed it?

@ai_/autoprefixers establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @ai_/autoprefixers — how do I know if it already compromised me?

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.

Is @ai_/autoprefixers part of a known attack campaign?

Yes — @ai_/autoprefixers is associated with the IN-MAL-2026-010872 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ai_/autoprefixers across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ai_/autoprefixers (version 1.2.0). 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.

Malicious package

@ai_/autoprefixersnpm

@ai_/autoprefixers is a confirmed malicious npm package (MAL-2026-11120) that opens a backdoor for remote access (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ai_/autoprefixers (npm)

MAL-2026-11120

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @ai_/autoprefixers

What this malware does

@ai_/autoprefixers is a typosquat of the popular autoprefixer package. On require, lib/autoprefixer.js loads node:child_process via a base64-hidden string (bm9kZTpjaGlsZF9wcm9jZXNz), fetches AES-256-CBC ciphertext over plain HTTP from http://player.sweeprovider.org/getKey.php and a key from http://player.sweeprovider.org/generateRandomKey.php, decrypts them using a helper (utils.prefixInfo) with a hardcoded key suffix 47e01aba1e12cf6d, and passes the plaintext to child_process.exec (also base64-hidden as ZXhlYw==). Any consumer that installs and imports this package receives arbitrary attacker-controlled shell command execution on their machine, with the C2 endpoint free to change the delivered payload at any time.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

5c2804af51ff476ec1ebdcec7b393366a66015ada2d2453a2acfbd21f99890f2

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ai_/autoprefixers (version 1.2.0). 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 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
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

No. @ai_/autoprefixers on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010872

References

npmjs.com

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 C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database