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

corstokennpm

Advisory published Updated

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

Malicious code in corstoken (npm)

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

What this malware does

The package corstoken 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 'corstoken' @ 2.14.7 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

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

Malicious versions

1 flagged
2.14.7

Indicators of compromise (SHA-256)

097340794c59c9f02cad5b4690aa47bc5011e379b30d8a9ac654913a38cca13f
a0d343f604565676254c8b24e997c84396038593cf5259c15d044ec3c5ab3350
d7d7cc0fd416fdcbdfe3517bbfd1ffec7e67ce88349fb17ddd2b22e408f740ed

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for corstoken (version 2.14.7).

  2. If you installed it — respond

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

Campaign

GHSA-4857-6w35-8677

References

Credits

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

Detect & block this

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

corstoken (npm) malicious package — MAL-2026-1051 | O3 Security