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

mysorenpm

Advisory published Updated

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

Malicious code in mysore (npm)

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

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)

d43be70370736ca8b84c1970096f8fd11d1805105c5965d7d936aa1b64d686f6

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove mysore 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 mysore 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. mysore 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-5x76-vjm4-f469

References

Detect & block this

O3 blocks mysore-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

mysore (npm) malicious package — MAL-2026-20239 | O3 Security