NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

autotel-edgenpm

Advisory published Updated

autotel-edge is a confirmed malicious npm package (MAL-2026-5220) that steals credentials and exfiltrates sensitive data (malicious version 3.16.13). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in autotel-edge (npm)

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

What this malware does

No concrete installer-harm signals were identified in this package version. No lifecycle hooks, hardcoded exfiltration endpoints, credential-path reads, or dropper patterns were surfaced. With no corroborating evidence of malicious behavior, a published block is not warranted; routing to human review so a reviewer can complete coverage and confirm benign intent or escalate if a specific harmful code path is identified.

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

1 flagged
3.16.13

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
811b38cb7e91f18a899293fc6cd657bdc63f07714d5277920cfc21532b5aca08

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for autotel-edge (version 3.16.13).

  2. If you installed it — respond

    autotel-edge 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-edge was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. autotel-edge on npm has been identified as a malicious package (version 3.16.13 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008644

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks autotel-edge-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-edge (npm) malicious package — MAL-2026-5220 | O3 Security