Malicious Code Detected in autotorch Package - Immediate Action Required

autotorch Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15123: Malicious code in autotorch (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The autotorch package is a tool designed for automating the training of machine learning models. It simplifies the process of model selection and hyperparameter tuning, making it a valuable resource for developers in the AI and machine learning community. However, a recent discovery has revealed that this package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the autotorch package stems from the inclusion of malicious code that can compromise user systems. This code may lead to unauthorized access, data theft, or other harmful actions. The issue was introduced in version 0 and affects all subsequent versions. Users are advised to take immediate action to mitigate potential risks associated with this vulnerability.

How To Fix

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

npm uninstall autotorch

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 measure, users can remove the autotorch package from their project until a secure version is released. This can be done with the following command: 'npm uninstall autotorch'. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the autotorch package poses a serious threat to users. Immediate action is required to mitigate risks, including updating or uninstalling the package. Stay vigilant and monitor for updates to ensure the security of your applications.

See every vulnerability recorded for autotorch →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, putting user systems at risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider uninstalling the package and using an alternative solution until a secure version is available.

Regularly check the package repository on npm or GitHub for announcements regarding updates and security patches.

While the risk of data loss depends on how the malicious code operates, it is advisable to review your system for any unauthorized changes or data breaches.

How To Fix

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

npm uninstall autotorch

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