Which versions of @2011-08-19/n are malicious?

The following npm versions of @2011-08-19/n are flagged malicious: 99.9.9, 99.9.10. Treat any of these as compromised.

How do I remediate @2011-08-19/n if I installed it?

Remove @2011-08-19/n 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 @2011-08-19/n — how do I know if it already compromised me?

If @2011-08-19/n 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 @2011-08-19/n part of a known attack campaign?

Yes — @2011-08-19/n is associated with the RLMA-2026-04657, RLUA-2026-05777 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 @2011-08-19/n across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @2011-08-19/n (2 malicious versions).

Malicious package

@2011-08-19/nnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@2011-08-19/n is a confirmed malicious npm package (MAL-2026-7033) that executes malicious code on install (malicious versions 99.9.9, 99.9.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @2011-08-19/n (npm)

MAL-2026-7033

Immediate action

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

npm uninstall @2011-08-19/n

Malicious versions

2 flagged

99.9.999.9.10

Indicators of compromise (SHA-256)

8c4c86fc32539ba47333148997c24521dd52f69131781f79357eb46a0bf6dd92

1e0c702bc642feadbb6e7d34acb96381329e063e75cd182e90eab24ec0e46862

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @2011-08-19/n (2 malicious versions).
If you installed it — respond
Remove @2011-08-19/n 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 @2011-08-19/n 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. @2011-08-19/n on npm has been identified as a malicious package (versions 99.9.9, 99.9.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04657RLUA-2026-05777

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @2011-08-19/n-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