Malicious Code Detected in autocat Package - Security Alert

autocat Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15112: Malicious code in autocat (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The autocat package is an npm library designed to facilitate automated tasks in JavaScript applications. It is commonly used for its ability to streamline workflows and enhance productivity. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the autocat package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of systems that utilize the package. Users are at risk of having their applications compromised, which can result in severe consequences, including data loss and reputational damage.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall autocat

If 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 temporary workaround, you can avoid using the autocat package altogether and explore alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing security measures such as code reviews and dependency scanning to mitigate potential threats.

Conclusion

The discovery of malicious code in the autocat package poses a serious threat to users. It is essential to take immediate action by removing the package and monitoring for any potential impacts on your applications. Stay informed about updates and consider using tools like Vulert to enhance your security posture.

See every vulnerability recorded for autocat →

Share this vulnerability

FAQ

The autocat package is an npm library used for automating tasks in JavaScript applications, enhancing workflow efficiency.

The malicious code was identified by security researchers from Amazon Inspector, who conducted a thorough analysis of the package.

Using the autocat package can lead to unauthorized access, data breaches, and exploitation of your application, compromising its security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

Immediately remove the autocat package from your project and monitor your application for any unusual activity. Consider using alternative packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall autocat

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback