Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

consumerwebnpm

Advisory published Updated

consumerweb is a confirmed malicious npm package (MAL-2026-10181) that steals credentials and exfiltrates sensitive data (malicious version 2200.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in consumerweb (npm)

MAL-2026-10181
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall consumerweb

What this malware does

On npm install, both preinstall and postinstall lifecycle hooks execute index.js, which collects host reconnaissance (os.hostname(), os.userInfo().username, os.homedir(), current working directory, DNS servers from dns.getServers(), and package metadata) and exfiltrates it via DNS lookup and an HTTPS POST to a subdomain of oast.fun (interact.sh OAST collaborator). The package name and description ('Internal App bUg b0UntY gollum22 h1') indicate a dependency-confusion attempt targeting an internal package name; any successful install both confirms the internal name is squattable and leaks identifying information about the installer's environment to the attacker's collaborator. No installer opt-in, no legitimate use case for the collected data going to an OAST endpoint.

Malicious versions

1 flagged
2200.4.2

Indicators of compromise (SHA-256)

74612bbfc323641d0141b4f1b495d6ea5f9b52129f2391bf21c5fabf63702ca7
87cc833287039635efd311bbe4ea455585c4d16ed331362cfa29b91d41d44680
41138153a17c3fec2022903c96e0c3646b85fd2ab21cbfc7162d6808952d4359

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for consumerweb (version 2200.4.2).

  2. If you installed it — respond

    consumerweb is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If consumerweb 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. consumerweb on npm has been identified as a malicious package (version 2200.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009726RLMA-2026-05521RLUA-2026-06164

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks consumerweb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

consumerweb (npm) malicious package — MAL-2026-10181 | O3 Security