Which versions of @w2d/web-components are malicious?

The following npm versions of @w2d/web-components are flagged malicious: 2.999.999. Treat any of these as compromised.

How do I remediate @w2d/web-components if I installed it?

@w2d/web-components 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 @w2d/web-components — how do I know if it already compromised me?

If @w2d/web-components 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 @w2d/web-components part of a known attack campaign?

Yes — @w2d/web-components is associated with the IN-MAL-2026-005370, IN-MAL-2026-005371 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 @w2d/web-components across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @w2d/web-components (version 2.999.999).

Malicious package

@w2d/web-componentsnpm

Advisory published Jun 11, 2026Updated Jun 11, 2026

@w2d/web-components is a confirmed malicious npm package (MAL-2026-5541) that steals credentials and exfiltrates sensitive data (malicious version 2.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @w2d/web-components (npm)

MAL-2026-5541

Immediate action

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

npm uninstall @w2d/web-components

What this malware does

The package targets the @w2d scope with an artificially high version (2.999.999) — the canonical dependency-confusion shape designed to outrank an internal registry's real package. On npm install, postinstall.js collects host identity (os.hostname(), os.userInfo(), process.cwd(), process.platform), base64-encodes the payload, and exfiltrates it to a hardcoded Burp Collaborator OAST domain 929u6o01dc28rl4mend089t9b0hr5ht6.oastify.com over both HTTPS GET (postinstall.js:28) and DNS lookup (postinstall.js:31). Comments in the file self-describe the package as a dependency-confusion PoC against Allwyn AG / win2day. Regardless of the author's stated bug-bounty framing, any installer whose registry configuration resolves the public @w2d/web-components instead of the intended internal package will silently beacon host/user/cwd identifiers to the attacker-controlled OAST host on install.

Malicious versions

1 flagged

2.999.999

Indicators of compromise (SHA-256)

2b8292b80f3e692b249561a14d94d2dfa0196f2377e7eee027b8dd630d251bd1

c6caf705e5dc4933e633197662744ab0909b77a70e12276408b155e89bbd5fc7

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-005370IN-MAL-2026-005371

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @w2d/web-components-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