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

automation_modelnpm

Advisory published Updated

automation_model is a confirmed malicious npm package (MAL-2025-191066) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.491, 1.0.781-stage, 1.0.895-dev). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in automation_model (npm)

MAL-2025-191066
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall automation_model

What this malware does

The package automation_model was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

3 flagged
1.0.4911.0.781-stage1.0.895-dev

Indicators of compromise (SHA-256)

b6b4ab86b995aa30207899784d17feba68bd397866ebb733d0de222eeb2a4c17
639370e1d34951d64c4ba1a352c6ce761b35f505502bc3ac59ed05c1a53404b9
1926379efdd9fddb153965f44070e510b81ea958a611dc7b2fafb891b856f35c

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for automation_model (3 malicious versions).

  2. If you installed it — respond

    automation_model 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 automation_model 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. automation_model on npm has been identified as a malicious package (versions 1.0.491, 1.0.781-stage, 1.0.895-dev flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3fxp-wv67-62xv

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

automation_model (npm) malicious package — MAL-2025-191066 | O3 Security