Critical Malicious Code Vulnerability in preset-classic Package

preset-classic Updated 02 Oct 2025

Summary

25/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6246: Malicious code in preset-classic (npm). Affects preset-classic versions 1.0.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 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 preset-classic package is an npm library designed to provide a set of pre-configured settings for various JavaScript projects. It is widely used for streamlining development processes and enhancing productivity. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant threat to developers and organizations relying on it.

Vulnerability Detail

The vulnerability in the preset-classic package stems from the presence of embedded malicious code, which can lead to complete system compromise. This code can exfiltrate sensitive information, manipulate system processes, and potentially allow unauthorized access to the affected machine. The origin of this vulnerability is linked to the package's malicious intent, as indicated by its classification in the Open Source Vulnerability database. Users who have this package installed should consider their systems fully compromised and take immediate action to mitigate the risks.

How To Fix

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

npm uninstall preset-classic

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

Currently, the only effective workaround is to completely uninstall the preset-classic package from your system. Ensure that you rotate any secrets or keys that may have been compromised due to the installation of this package.

Conclusion

The preset-classic package contains malicious code that poses a severe threat to any system it is installed on. Immediate action is required to uninstall the package and secure any compromised information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for preset-classic →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Keeping the package installed poses significant risks, including unauthorized access to your system and potential data breaches.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Rotating secrets is crucial to prevent unauthorized access to your systems and to mitigate the impact of any potential data breaches.

How To Fix

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

npm uninstall preset-classic

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