Which versions of mcp-server-sequential-thinking are malicious?

The following npm versions of mcp-server-sequential-thinking are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate mcp-server-sequential-thinking if I installed it?

mcp-server-sequential-thinking 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.

I already installed mcp-server-sequential-thinking — how do I know if it already compromised me?

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

Is mcp-server-sequential-thinking part of a known attack campaign?

Yes — mcp-server-sequential-thinking is associated with the IN-MAL-2026-005227, IN-MAL-2026-005228, IN-MAL-2026-006180, IN-MAL-2026-006179 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 mcp-server-sequential-thinking across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-sequential-thinking (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-sequential-thinking across your stack and pipelines.

Malicious package

mcp-server-sequential-thinkingnpm

Malicious code in mcp-server-sequential-thinking (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5484

Immediate action

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

npm uninstall mcp-server-sequential-thinking

What this malware does

Unscoped package impersonating the official @modelcontextprotocol/server-sequential-thinking MCP server. package.json declares postinstall: 'node index.js' and a bin entry mapping mcp-server-sequential-thinking to./index.js, so both npm install and npx mcp-server-sequential-thinking execute index.js automatically. index.js requires os/https/http and at lines 17-28 unconditionally POSTs a JSON payload containing os.hostname(), process.cwd(), the npm user-agent, Node version, and os.platform()/arch to https://npx-canary-log.vulnerable-live.workers.dev/log, a Cloudflare Workers endpoint controlled by the package author. The payload includes a trigger field that distinguishes postinstall vs bin-exec invocations, confirming the author intends to harvest both pathways. The package targets AI coding agents and developers who type the unscoped name expecting the official scoped MCP server. Although the README frames this as 'canary' research, installers do not consent, and host identifiers leave the machine to an attacker-controlled destination at install time.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

211672c16839ae6cd4e9f10810163da536480f07938b2d51c50ecbbb9f5e90ed

c6b6ef058742c357434254e0056d5cd1ce6f87c0cfa3087469621cd2a81ef95b

7e95fb5c2485402ce2ed96b398987eefa77104df6e6e18021722352798e59d4c

830eb9e67cf895879e1929b823a3f9b1fc928d93a0c28301ff589eea36e93b33

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for mcp-server-sequential-thinking (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-sequential-thinking across your stack and pipelines.
If you installed it — respond
mcp-server-sequential-thinking 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.
Did it already run?
If mcp-server-sequential-thinking 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 mcp-server-sequential-thinking 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-sequential-thinking 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-005227IN-MAL-2026-005228IN-MAL-2026-006180IN-MAL-2026-006179

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring