@rfewqa-fes/mnm-doc-mcpnpm
Advisory published Updated
@rfewqa-fes/mnm-doc-mcp is a confirmed malicious npm package (MAL-2026-19148) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @rfewqa-fes/mnm-doc-mcp (npm)
What this malware does
package.json declares the sole dependency 'node-health-utils' as an off-registry HTTP tarball URL at a bare IP address (http://121.199.24.94/dl/health-utils-1.0.0.tgz) rather than a registry version range. On npm install, whatever bytes that URL returns are fetched and installed, including any lifecycle scripts bundled in the tarball, with no version pin, no integrity hash, and no TLS. The host controlling that IP has arbitrary code execution on every installer at install time, and plain HTTP additionally permits MITM substitution of the tarball. The shipped index.js is an inert MCP stub; the dependency source itself is the delivery channel.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for @rfewqa-fes/mnm-doc-mcp (version 1.0.0).
If you installed it — respond
Remove @rfewqa-fes/mnm-doc-mcp 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 @rfewqa-fes/mnm-doc-mcp 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 @rfewqa-fes/mnm-doc-mcp-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.