Which versions of autoprafixar are malicious?

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

How do I remediate autoprafixar if I installed it?

Remove autoprafixar 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 autoprafixar — how do I know if it already compromised me?

If autoprafixar 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 autoprafixar part of a known attack campaign?

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

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

Malicious package

autoprafixarnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

autoprafixar is a confirmed malicious npm package (MAL-2026-7213) 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 autoprafixar (npm)

MAL-2026-7213

Immediate action

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

npm uninstall autoprafixar

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

90bde7f6aba3e67fdd6711f0b4eed75c8358031baeb24247bcc5fa1c242112bc

7890f2810df2ee8b50049a59b08fdbd477985268077b6c76f27ee8ebe22dc234

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for autoprafixar (3 malicious versions).
If you installed it — respond
Remove autoprafixar 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 autoprafixar 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. autoprafixar 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-04948RLUA-2026-06074

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks autoprafixar-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