Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@woodpecker-web-shared/componentsnpm

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

Malicious code in @woodpecker-web-shared/components (npm)

MAL-2026-16354
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @woodpecker-web-shared/components

What this malware does

On npm install, the package's postinstall hook runs node index.js, which collects installer host identifiers (os.hostname(), os.userInfo().username, os.platform(), architecture, cwd, node version, npm_lifecycle_event) and POSTs them as JSON to a hardcoded third-party collector at https://webhook.site/d9bc4bcc-ce74-4193-ae4e-96d234bb2220. The payload includes a src: 'loMesb' tag consistent with a campaign identifier used to correlate exfiltrated data across victims. The @woodpecker-web-shared/components scope/name has no legitimate reason to transmit installer identity to an anonymous webhook collector at install time, and the behavior fires automatically without user interaction. This is a recon beacon consistent with a dependency-confusion or typosquat lure.

Malicious versions

1 flagged
2.20.5

Indicators of compromise (SHA-256)

5f5f21bcc5464689c5b7c70819eeca4ea481f76b5f7dac0358cfe2d967da235f

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @woodpecker-web-shared/components (version 2.20.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @woodpecker-web-shared/components across your stack and pipelines.

  2. If you installed it — respond

    @woodpecker-web-shared/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.

  3. Did it already run?

    If @woodpecker-web-shared/components 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.

  4. How O3 protects you

    O3 blocks @woodpecker-web-shared/components 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. @woodpecker-web-shared/components on npm has been identified as a malicious package (version 2.20.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020265

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @woodpecker-web-shared/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
@woodpecker-web-shared/components (npm) malicious package — MAL-2026-16354 | O3 Security