NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@guicai777/mcp-doctornpm

Advisory published Updated

@guicai777/mcp-doctor is a confirmed malicious npm package (MAL-2026-20295) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @guicai777/mcp-doctor (npm)

MAL-2026-20295
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @guicai777/mcp-doctor

What this malware does

The package ships bridge.bin (~866KB) as base64-encoded, XOR-obfuscated bytes. On Windows, index.js reads bridge.bin, base64-decodes it, XOR-decrypts it with a one-byte key taken from the first byte of the blob, writes the resulting PE to %LOCALAPPDATA%\mcp-doctor\mcp-bridge.exe, and spawns it detached with windowsHide: true and stdio: 'ignore'. Before dropping, the CLI fetches https://fix-mcp-bridge.com/v.json and only skips execution when the remote JSON returns active:false, giving the operator a remote kill-switch to time and target payload activation. The README additionally instructs users to run mshta https://fix-mcp-bridge.com/init, a LOLBAS technique that downloads and executes remote HTML/JS/VBScript from the same author-controlled domain under the user's context. There is no legitimate build-time reason to base64+XOR a Windows binary the package itself owns; the encoding exists solely to conceal the payload's contents from scanners and reviewers, and the opaque PE is executed on the installer's host with no hash or signature verification. The combination of an obfuscated bundled executable, remote-gated drop-and-exec, and a documented out-of-band mshta remote-code-execution install path is a cover-story dropper masquerading as an MCP diagnostic utility.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

239993ae4c14c460d6ee1558bb2808072cf850d91c451fe950752387d4edb179
d1e1443947c2ad370530f2fd605f5286fbbebc8cbf4b2567cfe09db6d1901b3d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @guicai777/mcp-doctor (version 1.0.1).

  2. If you installed it — respond

    Remove @guicai777/mcp-doctor 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.

  3. Did it already run?

    If @guicai777/mcp-doctor 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. @guicai777/mcp-doctor on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022951GHSA-h82f-cjm4-g22r

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @guicai777/mcp-doctor-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.

Explore

@guicai777/mcp-doctor (npm) malicious package — MAL-2026-20295 | O3 Security