Critical Malicious Code Vulnerability in preset-log Package

preset-log Updated 02 Oct 2025

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5791: Malicious code in preset-log (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 preset-log package is an npm library designed for logging purposes in JavaScript applications. It provides developers with a simple interface to log messages, errors, and other information. However, this package has been identified to contain malicious code, which poses a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of embedded malicious code within the preset-log package. This code can compromise the security of any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall preset-log

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 workaround, ensure that all secrets and keys stored on the affected computer are rotated immediately from a different, secure computer. This action helps mitigate the risk of unauthorized access to sensitive information.

Conclusion

The preset-log package contains embedded malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Monitoring tools like Vulert can help keep your applications safe from future vulnerabilities.

See every vulnerability recorded for preset-log →

Share this vulnerability

FAQ

preset-log is an npm package used for logging in JavaScript applications, allowing developers to log messages and errors easily.

The malicious code can compromise your system's security, potentially allowing unauthorized access to sensitive information and control over your computer.

You should immediately remove the preset-log package from your project and rotate any secrets or keys stored on the affected system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall preset-log

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