Which versions of @prime0/pcomatch are malicious?

The following npm versions of @prime0/pcomatch are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @prime0/pcomatch if I installed it?

@prime0/pcomatch 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 @prime0/pcomatch — how do I know if it already compromised me?

If @prime0/pcomatch 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.

Is @prime0/pcomatch part of a known attack campaign?

Yes — @prime0/pcomatch is associated with the IN-MAL-2026-020073 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 @prime0/pcomatch across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @prime0/pcomatch (version 1.0.0).

Malicious package

@prime0/pcomatchnpm

Advisory published Sep 16, 2026Updated Sep 16, 2026

@prime0/pcomatch is a confirmed malicious npm package (MAL-2026-16206) 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/pcomatch (npm)

MAL-2026-16206

Immediate action

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

npm uninstall @prime0/pcomatch

What this malware does

index.js and the postinstall lifecycle script contact a hardcoded bare-IP endpoint at http://69.48.229.140:8080 over plain HTTP. On npm install, the postinstall hook collects host identifiers (hostname, username, platform, arch, cwd, node version, pid, all non-internal IP addresses, uptime, package name) and POSTs them as JSON to /b. On require() of the package main, the module beacons the same host, then polls /c every 30 seconds for JSON commands and executes the c field via child_process.exec, POSTing stdout/stderr back to /r. A source comment self-identifies the module as a stealth typosquat agent, while package.json advertises only a generic "small utility" description.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

08299e41eb4feb9e324854bf5cd3386e6e52696b4b11443254374897a1ad3816

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-020073

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @prime0/pcomatch-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