Which versions of autoprethixer are malicious?

The following npm versions of autoprethixer are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate autoprethixer if I installed it?

Remove autoprethixer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed autoprethixer — how do I know if it already compromised me?

If autoprethixer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is autoprethixer part of a known attack campaign?

Yes — autoprethixer is associated with the RLMA-2026-04949, RLUA-2026-06075 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 autoprethixer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for autoprethixer (3 malicious versions).

Malicious package

autoprethixernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

autoprethixer is a confirmed malicious npm package (MAL-2026-7214) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in autoprethixer (npm)

MAL-2026-7214

Immediate action

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

npm uninstall autoprethixer

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

30be37dd8eac21963f729299b9cf22b93b0d2ffe4836b980dcf257163c98de81

6393e567528d876156ee2242cc35f15dc824e5bf3acb45711082b82352f6121c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for autoprethixer (3 malicious versions).
If you installed it — respond
Remove autoprethixer from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If autoprethixer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. autoprethixer on npm has been identified as a malicious package (versions 1.1.2, 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04949RLUA-2026-06075

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks autoprethixer-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database