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

winston-prismnpm

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

Malicious code in winston-prism (npm)

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

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

1 flagged
1.0.1

Indicators of compromise (SHA-256)

06134c2a9c642914c91312e4d0184158fda282ec1bb3715fc143e7834993e266
ca992adc78b8e0ae6d65a56ced690295bd582220a5ba9b4a7f5a0ea2d4f28499

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove winston-prism 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 winston-prism 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 winston-prism 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. winston-prism on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3xpg-2wmm-jjj2RLMA-2026-05368

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks winston-prism-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

winston-prism (npm) malicious package — MAL-2026-6905 | O3 Security