Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mcp-server-figmanpm

mcp-server-figma is a confirmed malicious npm package (MAL-2026-5477) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mcp-server-figma (npm)

MAL-2026-5477
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mcp-server-figma

What this malware does

Package squats the unscoped name mcp-server-figma, which AI coding agents and developers commonly invoke via npx mcp-server-figma expecting the legitimate Figma MCP server (which uses a scoped name). The package.json declares scripts.postinstall: node index.js, which fires automatically on npm install. index.js (line 18) hardcodes ENDPOINT = 'https://npx-canary-log.vulnerable-live.workers.dev/log' and POSTs a JSON payload containing os.hostname(), process.cwd(), process.env.npm_config_user_agent, Node version, os.platform(), and a timestamp to that Cloudflare Workers endpoint. The README acknowledges the package is a deliberate name-squat used to capture traffic intended for a different package. Whether framed as research or not, the installer has not consented to having their hostname, working directory, and npm client identity transmitted to a third-party endpoint at install time. The combination of name-confusion targeting (squat of a name expected by agent tooling) plus install-time exfiltration of host metadata is the typosquat-with-payload pattern.

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

2 flagged
0.0.10.0.2

Indicators of compromise (SHA-256)

29060c34630f9510a380d9a36111d525f2b33db41ee4d079e7d63b3e7c697c76
474223e0d5456564c1ae112031e3b8f276850a79f59cc93ed3a04805de291f20
907890012c3e47c5c0a67ab7f1d2c9a5f0c913aeb6fabf95c8f53c5954f33a91
ae79ea626ab6479ab2b5bec20a357cf44dac76f2603e0cf0c0afc34fe9550395
cd1c640ad7c3eb7e2850f240d9920938e882d57fd57ac25419f7a0eb5d73f76d

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-figma (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mcp-server-figma across your stack and pipelines.

  2. If you installed it — respond

    mcp-server-figma is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If mcp-server-figma 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.

  4. How O3 protects you

    O3 blocks mcp-server-figma 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

No. mcp-server-figma on npm has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005226IN-MAL-2026-005225IN-MAL-2026-005792IN-MAL-2026-005793GHSA-8j33-qh42-vjc6

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mcp-server-figma-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

mcp-server-figma (npm) malicious package — MAL-2026-5477 | O3 Security