Which versions of fa-mcp-sdk are malicious?

The following npm versions of fa-mcp-sdk are flagged malicious: 0.12.72. Treat any of these as compromised.

How do I remediate fa-mcp-sdk if I installed it?

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.

I already installed fa-mcp-sdk — how do I know if it already compromised me?

If fa-mcp-sdk 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.

Is fa-mcp-sdk part of a known attack campaign?

Yes — fa-mcp-sdk is associated with the IN-MAL-2026-015101 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 fa-mcp-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fa-mcp-sdk (version 0.12.72).

Malicious package

fa-mcp-sdknpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

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)

MAL-2026-12789

Immediate action

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

npm uninstall fa-mcp-sdk

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

1 flagged

0.12.72

Indicators of compromise (SHA-256)

62142cbcb6da6a6c078dd91a92cc28d8cfa30a9f4fc901ab2cdbc4cfd6540abb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for fa-mcp-sdk (version 0.12.72).
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 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. fa-mcp-sdk on npm has been identified as a malicious package (version 0.12.72 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015101

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database