registry  /  nodemon-slint  /  3.1.13

nodemon-slint@3.1.13

OSV Malicious Advisory

scanned 2h ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-10117 confirms this npm version as malicious. 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...

Advisory
MAL-2026-10117
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in nodemon-slint (npm)
Details
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. ## Source: ghsa-malware (25919cd9abbeb6b978466e7fb9d006c38d61ff9c3d238f1b3ddffc6809ca819e) 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.
Decision reason
No blocking static signals were detected.

Decision evidence

public snapshot
Behavioral surface
Source
ChildProcessDynamicRequireEnvironmentVarsFilesystemShell
Supply chain
UrlStrings
ManifestNo manifest risk signals triggered.
scanned 27 file(s), 82.2 KB of source, external domains: git.io, github.com

Source & flagged code

2 flagged · loading source
bin/nodemon.jsView file
2L3: const cli = require('../lib/cli'); L4: const nodemon = require('../lib/');
Medium
Dynamic Require

Package source references dynamic require/import behavior.

bin/nodemon.jsView on unpkg · L2
bin/windows-kill.exeView file
path = bin/windows-kill.exe kind = native_binary sizeBytes = 80384 magicHex = [redacted]
Medium
Ships Native Binary

Package ships native binary artifacts.

bin/windows-kill.exeView on unpkg

Findings

4 Medium3 Low
MediumDynamic Requirebin/nodemon.js
MediumEnvironment Vars
MediumShips Native Binarybin/windows-kill.exe
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowUrl Strings