Which versions of nodemon-slint are malicious?

The following npm versions of nodemon-slint are flagged malicious: 3.1.13. Treat any of these as compromised.

How do I remediate nodemon-slint if I installed it?

nodemon-slint is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed nodemon-slint — how do I know if it already compromised me?

If nodemon-slint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nodemon-slint part of a known attack campaign?

Yes — nodemon-slint is associated with the GHSA-wr24-8cj8-p627, IN-MAL-2026-009804 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nodemon-slint across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-slint (version 3.1.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodemon-slint across your stack and pipelines.

Malicious package

nodemon-slintnpm

nodemon-slint is a confirmed malicious npm package (MAL-2026-10117) that steals credentials and exfiltrates sensitive data (malicious version 3.1.13). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nodemon-slint (npm)

MAL-2026-10117

Immediate action

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

npm uninstall nodemon-slint

What this malware does

Package name, README, homepage (nodemon.io), author (remy), and source tree are copied verbatim from the widely-used 'nodemon' package, with the addition of a single novel runtime dependency 'type-slint' (^3.3.7) declared in package.json. That dependency is never imported by any file reachable from the declared main (lib/nodemon.js) or from bin/, so it serves no functional purpose within this package. The only installer-facing effect of the manifest change relative to nodemon is that 'npm install nodemon-slint' also resolves and installs 'type-slint' into the installer's dependency tree, where any install-time hooks or load-time side effects it contains will run. The host package itself does not exhibit exfiltration, install-time RCE, or backdoor behavior in its own code; the risk is carried by the co-installed sibling. Name similarity to 'nodemon' (a top-tier package) plus injection of an unreferenced dependency is the namespace-abuse / typosquat-dropper shape.

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

1 flagged

3.1.13

Indicators of compromise (SHA-256)

25919cd9abbeb6b978466e7fb9d006c38d61ff9c3d238f1b3ddffc6809ca819e

5488028be686500c0af6b7f91ead55be9ddaeb86f3b920fce7eed6f8111b0050

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nodemon-slint (version 3.1.13). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nodemon-slint across your stack and pipelines.
If you installed it — respond
nodemon-slint is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If nodemon-slint was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nodemon-slint before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nodemon-slint on npm has been identified as a malicious package (version 3.1.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wr24-8cj8-p627IN-MAL-2026-009804

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nodemon-slint-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database