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

silverminenpm

Advisory published Updated

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

Malicious code in silvermine (npm)

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

What this malware does

The package silvermine was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'silvermine' @ 99.99.1 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.99.1

Indicators of compromise (SHA-256)

48fc132683cbda84aa98d77c10d2116dabdac6bc7598a5b60d2b25cb2374bd2e
3b977fbc50506142e7db68fc536bdfd96ccfa135ff0c03f3957d24b716cc4441
194377d773e651f6f01c9662fac716fb338b55f83baafc1c503b692fe1195e5a

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for silvermine (version 99.99.1).

  2. If you installed it — respond

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

Campaign

GHSA-g37j-jvxp-qrjv

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

silvermine (npm) malicious package — MAL-2026-257 | O3 Security