Which versions of your-unique-package-name1337 are malicious?

The following npm versions of your-unique-package-name1337 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate your-unique-package-name1337 if I installed it?

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

If your-unique-package-name1337 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 your-unique-package-name1337 part of a known attack campaign?

Yes — your-unique-package-name1337 is associated with the RLMA-2026-05656, RLUA-2026-06559 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 your-unique-package-name1337 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for your-unique-package-name1337 (version 1.0.0).

Malicious package

your-unique-package-name1337npm

Advisory published Jul 20, 2026Updated Sep 1, 2026

your-unique-package-name1337 is a confirmed malicious npm package (MAL-2026-10906) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in your-unique-package-name1337 (npm)

MAL-2026-10906

Immediate action

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

npm uninstall your-unique-package-name1337

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1ef16648bda3ed3c9437c95016d5c67f86900ed53cb57f6aeb292553ddfd7f0d

8aabf6ff1b9d3e8269afe5417fac5afe94b66247fc662c2b097353d7fee4955a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for your-unique-package-name1337 (version 1.0.0).
If you installed it — respond
Remove your-unique-package-name1337 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 your-unique-package-name1337 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. your-unique-package-name1337 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05656RLUA-2026-06559

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks your-unique-package-name1337-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