Which versions of consumerweb-risk are malicious?

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

How do I remediate consumerweb-risk if I installed it?

consumerweb-risk 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-risk — how do I know if it already compromised me?

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

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

Malicious package

consumerweb-risknpm

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

Malicious code in consumerweb-risk (npm)

MAL-2026-11269

Immediate action

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

npm uninstall consumerweb-risk

What this malware does

The package's preinstall lifecycle script runs automatically on npm install. It collects the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working directory (process.cwd()), serializes them to JSON, hex-encodes the payload, chunks it into DNS subdomain labels, and issues dns.lookup() queries against an attacker-controlled nameserver under jgl.red. The lookups themselves carry the encoded host identity out to the attacker's authoritative DNS server, forming a covert DNS-tunnel exfiltration channel that fires on every install regardless of whether the module is ever required.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

3.4.3

Indicators of compromise (SHA-256)

0e5f4efb70659109081158cdf1172001c3a589dbac63414af7c04485d40e42d0

aa886e4b335d3fc76fa6bc8e50c2e428ac164165830705c0ab2847857c2b3aa7

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-risk (version 3.4.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging consumerweb-risk across your stack and pipelines.
If you installed it — respond
consumerweb-risk 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-risk 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-risk 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-risk on npm has been identified as a malicious package (version 3.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5439-r8p8-2gmxIN-MAL-2026-011149

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks consumerweb-risk-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