NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

winjb6npm

Advisory published Updated

winjb6 is a confirmed malicious npm package (MAL-2026-18573) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in winjb6 (npm)

MAL-2026-18573
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall winjb6

What this malware does

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

66f25810500ddba52e0ffb1e34dbe95bf1d2bc99313c6c687740d0e7f6222f3b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for winjb6 (all published versions).

  2. If you installed it — respond

    Remove winjb6 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 activity or persistence.

  3. Did it already run?

    If winjb6 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. winjb6 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qhmw-9qw2-5x8x

References

Detect & block this

O3 blocks winjb6-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

winjb6 (npm) malicious package — MAL-2026-18573 | O3 Security