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?

Remove @w2d/web-components 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect @w2d/web-components in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking @w2d/web-components and packages like it before any post-install script runs.

Malicious package

@w2d/web-componentsnpm

Malicious code in @w2d/web-components (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection