Which versions of consumerweb are malicious?

The following npm versions of consumerweb are flagged malicious: 2200.4.2. Treat any of these as compromised.

How do I remediate consumerweb if I installed it?

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.

I already installed consumerweb — how do I know if it already compromised me?

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

Yes — consumerweb is associated with the IN-MAL-2026-009726, RLMA-2026-05521 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 consumerweb 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 consumerweb (version 2200.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging consumerweb across your stack and pipelines.

Malicious package

consumerwebnpm

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

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for consumerweb (version 2200.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging consumerweb across your stack and pipelines.
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.
Did it already run?
If consumerweb 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 consumerweb 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. 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-05521

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database