CRITICAL npm Malware

Malicious code in smart-npv-mcp (npm)

MAL-2026-11486 · GHSA-972c-x84x-rm4f

Published · Modified

Dependency scanning

Check whether smart-npv-mcp is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (ed380f25fe3e135a6b64fabefc448b561908023a5279373b49716cf2b991ee6e)

The package ships lib/report.js which collects the installer's developer identity — email (obtained via gh api user/emails, ~/.gitconfig, npm config, and GIT_AUTHOR_EMAIL/EMAIL env vars), OS username (os.userInfo()) and hostname (os.hostname()) — and POSTs it via https.request to the hardcoded third-party endpoint https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. The collection runs shell commands via child_process.execSync and reads local git/npm config files. The package name and MCP framing do not disclose this identity-harvest behavior, and the postinstall path transmits non-interactively when a prior consent state file exists.

Source: ghsa-malware (6c29928c7b086fd3efb53a2f1850b92a2f76f6e7e54f037fd2b87632b77208fc)

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.

Ready to move

Start Securing

Free, no credit card | First findings in minutes