Which versions of fetchcraft are malicious?

The following npm versions of fetchcraft are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate fetchcraft if I installed it?

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

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

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

Malicious package

fetchcraftnpm

Malicious code in fetchcraft (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10435

Immediate action

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

npm uninstall fetchcraft

What this malware does

package.json declares the runtime dependency node-runtime-utils as https://github.com/Hexa-devy/node-runtime-utils/archive/refs/heads/main.tar.gz — a tarball fetched from the mutable main branch of a personal GitHub user's repository, with no commit SHA, tag, or integrity hash pinning. On npm install fetchcraft, npm downloads and installs whatever bytes that URL serves at install time, including any lifecycle scripts (preinstall/install/postinstall/prepare) shipped in the fetched tarball. Because the source is a mutable branch under a personal account rather than a registry-published package or a pinned commit, the contents can be swapped at any time without any change to fetchcraft itself, allowing arbitrary code to be executed on the installer's machine. The dependency is not referenced by the package's exported code, giving it no legitimate functional purpose.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

72eb80237f1255f009a3dd04cff4ec9b6b2c569088f487ab56b6924ce3f721c7

c1a40f1af8ba957a18b37ddba0dbe5634112f489841b22208eff421f9a09f786

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 fetchcraft (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fetchcraft across your stack and pipelines.
If you installed it — respond
Remove fetchcraft 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 fetchcraft 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 fetchcraft 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. fetchcraft on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010223IN-MAL-2026-010221

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fetchcraft-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