Critical Malicious Code Vulnerability in jstoauto Package

jstoauto Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192815: Malicious code in jstoauto (npm). Affects jstoauto versions 5.1.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

jstoauto is an npm package designed to automate JavaScript tasks, providing developers with tools to streamline their workflows. It is widely used in various projects for its efficiency and ease of integration. However, recent findings have revealed that version 5.1.0 of jstoauto contains malicious code, posing significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code in the jstoauto package, specifically in version 5.1.0. This code can potentially compromise the integrity of applications, leading to unauthorized access, data breaches, or system manipulation. The malicious nature of this code can result in severe ramifications for developers and users alike, making it imperative to address this issue promptly.

How To Fix

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

npm uninstall jstoauto

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 may consider removing the jstoauto package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall jstoauto'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the jstoauto package version 5.1.0 presents a serious security threat to developers and users. It is crucial to update to a patched version or remove the package to safeguard applications from potential exploits. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for jstoauto →

Share this vulnerability

FAQ

jstoauto is an npm package used for automating JavaScript tasks, helping developers streamline their workflows.

Version 5.1.0 of jstoauto contains the malicious code vulnerability.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate updates are not possible, consider uninstalling the jstoauto package as a temporary measure to avoid exposure to the malicious code.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

How To Fix

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

npm uninstall jstoauto

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