Which versions of mcp-util-helpers are malicious?

The following npm versions of mcp-util-helpers are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate mcp-util-helpers if I installed it?

mcp-util-helpers 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 mcp-util-helpers — how do I know if it already compromised me?

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

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

Malicious package

mcp-util-helpersnpm

mcp-util-helpers is a confirmed malicious npm package (MAL-2026-13880) 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 mcp-util-helpers (npm)

MAL-2026-13880

Immediate action

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

npm uninstall mcp-util-helpers

What this malware does

On npm install, the preinstall hook (scripts/check-env.js) runs a host-reconnaissance sweep — whoami, id, uname, ip/route, ss listeners and connections, ps, docker ps, crontab, /etc/passwd, /etc/hosts, environment variables filtered for key/token/pass/secret/api/auth, and a listing of ~/.ssh/ — and POSTs the collected data via curl to a hardcoded webhook.site bucket at https://webhook.site/0c5803fc-bdd6-4dd0-8c57-68ee0cabac29/the analysis. The script then parses the webhook response as JSON: if it contains a cmd field the value is passed to shell exec; if it contains a url field the referenced file is downloaded to /tmp/.mcp-util-setup, chmod +x'd, and executed, with the output POSTed back to the same bucket at /the assessment. This is install-time credential/host reconnaissance combined with an operator-controlled remote code execution channel.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2044da43e53933094b69c1436146bdea64cbc4c011e4b8a141ceea0cab19eb5c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-util-helpers (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-util-helpers across your stack and pipelines.
If you installed it — respond
mcp-util-helpers 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 mcp-util-helpers 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 mcp-util-helpers 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. mcp-util-helpers 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-017567

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mcp-util-helpers-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