Which versions of web-nbq6lx are malicious?

The following npm versions of web-nbq6lx are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate web-nbq6lx if I installed it?

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

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

Yes — web-nbq6lx is associated with the RLMA-2025-05999 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 web-nbq6lx across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for web-nbq6lx (version 1.0.0).

Malicious package

web-nbq6lxnpm

Advisory published Dec 1, 2025Updated Dec 2, 2025

web-nbq6lx is a confirmed malicious npm package (MAL-2025-191601) 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 web-nbq6lx (npm)

MAL-2025-191601

Immediate action

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

npm uninstall web-nbq6lx

What this malware does

The package web-nbq6lx was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

eea338de7aa9db110123e1930a9d535ef53ed87ec88b7ccfca3e1b37575f021d

8ccf5295ee0874e2f3ca38f3477ff9d06518c7291910663851122f2774d0c481

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for web-nbq6lx (version 1.0.0).
If you installed it — respond
Remove web-nbq6lx 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 web-nbq6lx 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. web-nbq6lx 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-2025-05999

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks web-nbq6lx-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