@not-nemo/crypto-trackernpm
Advisory published Updated
@not-nemo/crypto-tracker is a confirmed malicious npm package (MAL-2026-2491) that executes malicious code on install (malicious versions 1.0.2, 1.0.4, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @not-nemo/crypto-tracker (npm)
What this malware does
The package @not-nemo/crypto-tracker 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 '@not-nemo/crypto-tracker' @ 1.0.4 (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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @not-nemo/crypto-tracker (3 malicious versions).
If you installed it — respond
Remove @not-nemo/crypto-tracker 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.
Did it already run?
If @not-nemo/crypto-tracker 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks @not-nemo/crypto-tracker-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.