MAL-2026-5541 Malicious code in @w2d/web-components (npm)
Malicious package
Published
MAL-2026-5541 is a malicious package: @w2d/web-components (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-5541/ (Markdown: https://insights.sbomify.com/MAL-2026-5541/index.md)
- Package
- @w2d/web-components
- Registry
- npm
What is MAL-2026-5541?
MAL-2026-5541 is a malicious package in @w2d/web-components, published on 11 Jun 2026.
Official description
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.What should I do about MAL-2026-5541?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.