fa-mcp-sdknpm
fa-mcp-sdk is a confirmed malicious npm package (MAL-2026-12789) that executes malicious code on install (malicious version 0.12.72). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fa-mcp-sdk (npm)
What this malware does
The package includes cli-template/update.cjs, an update helper that combines several install/update-time capabilities: it imports child_process, https, fs, and os; reads os.hostname() and other system identifiers; issues https.request POST calls to a remote endpoint; performs filesystem existence checks; and calls spawn('/bin/bash',...) to execute shell commands. The composition — host identifier collection, arbitrary shell execution via /bin/bash, and outbound HTTPS POST inside a self-updater — provides a mechanism to run remote-directed commands on machines that install or run this package. Additional files under dist/core/ (agent-tester/services/TesterMcpClientService.js, web/server-http.js) exercise ping/HTTP GET/POST patterns consistent with host reachability probing and outbound command/data flow.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fa-mcp-sdk (version 0.12.72). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fa-mcp-sdk across your stack and pipelines.
If you installed it — respond
Remove fa-mcp-sdk 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 fa-mcp-sdk 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 fa-mcp-sdk 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks fa-mcp-sdk-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.