Which versions of process-mite are malicious?

The following npm versions of process-mite are flagged malicious: 1.1.79. Treat any of these as compromised.

How do I remediate process-mite if I installed it?

Remove process-mite 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 process-mite — how do I know if it already compromised me?

If process-mite 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 process-mite part of a known attack campaign?

Yes — process-mite is associated with the IN-MAL-2026-020110 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 process-mite 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 process-mite (version 1.1.79). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging process-mite across your stack and pipelines.

Malicious package

process-mitenpm

process-mite is a confirmed malicious npm package (MAL-2026-16224) that executes malicious code on install (malicious version 1.1.79). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in process-mite (npm)

MAL-2026-16224

Immediate action

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

npm uninstall process-mite

What this malware does

On import of the package main, index.js auto-invokes an initialize() routine that spawns a detached node loader.js process. loader.js performs an HTTPS GET against the hardcoded endpoint https://api.npoint.io/33e8d008c334b060adad, base64-decodes the code field of the returned JSON, and executes the decoded string via new Function("require","__dirname","__filename","module","exports", decodedCode)(...), granting the fetched payload full Node.js capabilities on the installer's host. npoint.io is a user-editable JSON hosting service, so the executed code is mutable by whoever controls the note and is unpinned and unverified. package.json and README present the package as a 'runtime-utils' library exporting getRuntimeInfo, but no such API is shipped; the advertised purpose is a cover story for the dropper. In-source comments self-describe the module as an embedded remote-code-execution client.

Malicious versions

1 flagged

1.1.79

Indicators of compromise (SHA-256)

4763fac30373bc805351d0eb8e0989cde9dcd2ab2c1b18f9eb7bde4e61765191

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for process-mite (version 1.1.79). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging process-mite across your stack and pipelines.
If you installed it — respond
Remove process-mite 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 process-mite 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 process-mite 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. process-mite on npm has been identified as a malicious package (version 1.1.79 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020110

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks process-mite-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