Which versions of autotel are malicious?

The following npm versions of autotel are flagged malicious: 2.26.4, 3.4.3. Treat any of these as compromised.

How do I remediate autotel if I installed it?

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

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

Yes — autotel is associated with the IN-MAL-2026-008673, IN-MAL-2026-008669 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 autotel 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 autotel (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autotel across your stack and pipelines.

Malicious package

autotelnpm

autotel is a confirmed malicious npm package (MAL-2026-5211) that steals credentials and exfiltrates sensitive data (malicious versions 2.26.4, 3.4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in autotel (npm)

MAL-2026-5211

Immediate action

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

npm uninstall autotel

What this malware does

Pattern matches fired on co-occurrence of the strings 'ping', 'POST', and 'hostname' in the package's bundled and source files (dist/chunk-.cjs, dist/chunk-.js, dist/init-*.d.ts, src/init.ts). These are generic keywords that commonly appear together in observability/telemetry tooling without indicating exfiltration: 'ping' is frequently used for health-check endpoints, 'POST' for normal HTTP client code, and 'hostname' for environment/identity reporting in telemetry payloads. No hardcoded attacker-controlled C2 endpoint, credential-path read (~/.aws, ~/.ssh, ~/.npmrc, browser profiles), env-var scraping loop, install-time lifecycle hook, or import-time side effect has been corroborated. Routing to human review so a maintainer can confirm whether the POST destinations are user-configurable / vendor-documented telemetry endpoints versus a hardcoded exfil sink.

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

2 flagged

2.26.43.4.3

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb

808ef4e5611db8adab2b470eb14e82c8ccc277004480b3cbef590f724552097b

921a045507925f9accff44927ec74588991f03dd291a3ae95cdc9919523ed800

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 autotel (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autotel across your stack and pipelines.
If you installed it — respond
autotel 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 autotel 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 autotel 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 on npm has been identified as a malicious package (versions 2.26.4, 3.4.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008673IN-MAL-2026-008669

References

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database