Which versions of sd-notexsit are malicious?

The following npm versions of sd-notexsit are flagged malicious: 999.0.41. Treat any of these as compromised.

How do I remediate sd-notexsit if I installed it?

Remove sd-notexsit 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.

I already installed sd-notexsit — how do I know if it already compromised me?

If sd-notexsit 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.

How do I find sd-notexsit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for sd-notexsit (version 999.0.41).

Malicious package

sd-notexsitnpm

Advisory published Dec 4, 2025Updated Dec 8, 2025

sd-notexsit is a confirmed malicious npm package (MAL-2025-192348) that executes malicious code on install (malicious version 999.0.41). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sd-notexsit (npm)

MAL-2025-192348

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sd-notexsit

What this malware does

The package sd-notexsit was found to contain malicious code.

The OpenSSF Package Analysis project identified 'sd-notexsit' @ 999.0.41 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged

999.0.41

Indicators of compromise (SHA-256)

f4e913bd2265d51b2e2a3c9be6498c860ffc76186b24a2f81322c22d2c47a9b0

6af19b71c855e0821a174c728ee170ccd0e7c86e6d3f864fed1f638657ac11d9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for sd-notexsit (version 999.0.41).
If you installed it — respond
Remove sd-notexsit 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 sd-notexsit 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. sd-notexsit on npm has been identified as a malicious package (version 999.0.41 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks sd-notexsit-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database