Critical Malicious Code Vulnerability in automation_model Package
Summary
MAL-2025-191066: Malicious code in automation_model (npm). Affects automation_model versions 1.0.491 – 1.0.895-dev. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The automation_model package is an npm library designed for automating various tasks in software development. It provides developers with tools to streamline workflows and enhance productivity. However, this package has been compromised, leading to the inclusion of malicious code that poses significant security risks to any system utilizing it.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the automation_model package. This code can fully compromise any computer where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has manipulated the package, making it imperative for users to take immediate action to secure their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall automation_modelIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a workaround, users should consider isolating the affected system from the network to prevent further compromise. Additionally, running a comprehensive malware scan on the system may help identify and mitigate any remaining threats.
Conclusion
The automation_model package has been compromised with malicious code, posing serious security risks to users. Immediate removal of the package and rotation of sensitive information is crucial to mitigate potential damage. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for automation_model →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
While removing the package is essential, you should also rotate all sensitive information and conduct a thorough security audit of your system.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and further exploitation of your system.
Check the npm registry for any patched versions of the automation_model package and update accordingly.
