@prime0/inimatchnpm
Advisory published Updated
@prime0/inimatch is a confirmed malicious npm package (MAL-2026-16205) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @prime0/inimatch (npm)
What this malware does
@prime0/inimatch is a typosquat of minimatch that behaves as a stealth remote-access agent. postinstall.js runs on npm install and POSTs a host fingerprint (hostname, username, platform/arch, cwd, node version, pid, non-internal IPs, uptime, package name) to http://69.48.229.140:8080/b. index.js, on require(), beacons the same fingerprint to /b and then every 30 seconds polls http://69.48.229.140:8080/c?id=... for a JSON command, passes the returned command string to child_process.exec, and POSTs stdout/stderr back to /r, giving the operator of that host arbitrary shell execution on the installer's machine. A source comment self-identifies the package as a stealth-agent typosquat, while package.json advertises only a 'small utility'.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @prime0/inimatch (version 1.0.0).
If you installed it — respond
@prime0/inimatch 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 @prime0/inimatch 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
Detect & block this
O3 blocks @prime0/inimatch-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.