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

autotel-mcp-instrumentationnpm

autotel-mcp-instrumentation is a confirmed malicious npm package (MAL-2026-5224) that steals credentials and exfiltrates sensitive data (malicious versions 29.0.2, 30.0.5, 31.0.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in autotel-mcp-instrumentation (npm)

MAL-2026-5224
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall autotel-mcp-instrumentation

What this malware does

No concrete installer-harm signals were identified for this package version. No lifecycle hooks, network destinations, credential reads, or other supply-chain attack fingerprints were surfaced in the available evidence. Routing for human review given incomplete coverage; a reviewer should confirm the package's lifecycle scripts and main-module top-level behavior before publishing a verdict.

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.

The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.

Malicious versions

6 flagged
29.0.230.0.531.0.132.0.133.0.234.0.1

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
5c64859e391f8cefcdc5dd1b66f0364b7821a5dbc3f1493a5cfb4a168ad6a4cf
bd61230a4a25949c260d51264d579e631ddd2fbb4941cbd012441d33ef0cfe83
d430094afb9dc367c9a2a0477eea7bba4074cf3eed9f6f2861a0e82f79706ee4
eb20d53e0dd24d56001b04a9fdcc4b4dab8ab8d70a4bf881b6d2dd72a93f7f0b
42dd9975eca2191660b9c24b377e8b0ea69bdfe70159364c7b3e19634b1fc68a
584565adcb1b6940e9ce0a9bf1cfa84a75144a3ce4d0ebfea95b5ac347b984d0
8907d98bb2a7a3170baecc21403761fb7705c62c3d2343bd37b6e5990559aee5

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 autotel-mcp-instrumentation (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autotel-mcp-instrumentation across your stack and pipelines.

  2. If you installed it — respond

    autotel-mcp-instrumentation 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 autotel-mcp-instrumentation 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 autotel-mcp-instrumentation 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. autotel-mcp-instrumentation on npm has been identified as a malicious package (versions 29.0.2, 30.0.5, 31.0.1, 32.0.1, 33.0.2, 34.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7cv4-gfx4-2c3vIN-MAL-2026-008678IN-MAL-2026-008692IN-MAL-2026-008696IN-MAL-2026-008685IN-MAL-2026-008698IN-MAL-2026-008667

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks autotel-mcp-instrumentation-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

autotel-mcp-instrumentation (npm) malicious package — MAL-2026-5224 | O3 Security