Which versions of mcp-server-sentry are malicious?

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

How do I remediate mcp-server-sentry if I installed it?

mcp-server-sentry 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-sentry — how do I know if it already compromised me?

If mcp-server-sentry 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-sentry part of a known attack campaign?

Yes — mcp-server-sentry is associated with the IN-MAL-2026-005222, IN-MAL-2026-005221, IN-MAL-2026-006069, IN-MAL-2026-006070 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-sentry 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-sentry (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-sentry across your stack and pipelines.

Malicious package

mcp-server-sentrynpm

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

MAL-2026-5483

Immediate action

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

npm uninstall mcp-server-sentry

What this malware does

On npm install, the package's postinstall hook (scripts.postinstall: node index.js) collects host identifiers — os.hostname(), process.cwd(), the npm user-agent, Node version, and os.platform()/arch — and POSTs them to a hardcoded remote endpoint at https://npx-canary-log.vulnerable-live.workers.dev/log without any installer consent or opt-out. The package name mcp-server-sentry is an unscoped squat targeting the MCP/Sentry naming convention used by AI coding agents and developer tooling that invoke npx mcp-server-sentry expecting an official MCP server; the README confirms the package was published to capture traffic resolving this unclaimed name. The combination of an intentional name-squat plus install-time outbound transmission of installer identifiers (hostname + working-directory paths, which routinely leak usernames and project layouts) to an author-controlled Cloudflare Workers endpoint is a supply-chain exfiltration shape, regardless of the author's stated 'research canary' intent — installers receive no disclosure and no opportunity to decline before the beacon fires.

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

8958cba33d604713291f4f6c0a036afbf1e87ad5a4f07208e65b8b6c0c8925cd

cf12283b2f16a43388d0cc6c2991fbbdab0da44ab344c1f9c71515dd05024046

425687b3f3b3b2b66b87fc41473eeb1b8cc1ad435d9d3c8f9ba04e9bd4bd2900

d60e168b4e5a5d37ecf2e06734c5eea1440ebc8a224e6789b4b5b635e160cff2

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-sentry (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-sentry across your stack and pipelines.
If you installed it — respond
mcp-server-sentry 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-sentry 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-sentry 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-sentry 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-005222IN-MAL-2026-005221IN-MAL-2026-006069IN-MAL-2026-006070

References

Credits

Amazon Inspector · finder

Detect & block this

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