Which versions of a39a85e7 are malicious?

The following npm versions of a39a85e7 are flagged malicious: 1.9.0. Treat any of these as compromised.

How do I remediate a39a85e7 if I installed it?

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

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

Yes — a39a85e7 is associated with the RLMA-2024-10419, RLUA-2026-10668 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 a39a85e7 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 a39a85e7 (version 1.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a39a85e7 across your stack and pipelines.

Malicious package

a39a85e7npm

a39a85e7 is a confirmed malicious npm package (MAL-2024-11287) that executes malicious code on install (malicious version 1.9.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in a39a85e7 (npm)

MAL-2024-11287

Immediate action

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

npm uninstall a39a85e7

Malicious versions

1 flagged

1.9.0

Indicators of compromise (SHA-256)

b25cea46a57886b5590fa5f12519eece4f75d138c112d651eff1ca5276ccfdd8

73f292f2063ce8ab8268c6676b234ead5aba8e9f293e9cabd111c797b5bf905c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for a39a85e7 (version 1.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a39a85e7 across your stack and pipelines.
If you installed it — respond
Remove a39a85e7 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 a39a85e7 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 a39a85e7 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. a39a85e7 on npm has been identified as a malicious package (version 1.9.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-10419RLUA-2026-10668

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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