Critical Malicious Code Vulnerability in pretty-loggers Package

pretty-loggers Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1964: Malicious code in pretty-loggers (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 pretty-loggers package is an npm library designed to enhance logging capabilities in JavaScript applications. It provides developers with a simple interface to format and display log messages in a more readable manner. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the pretty-loggers package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected computer. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionality within the software. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall pretty-loggers

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, if you need logging functionality, consider using alternative logging packages that are known to be secure. Some popular alternatives include winston and bunyan. You can install them using npm as follows:

npm install winston

or

npm install bunyan

Conclusion

The pretty-loggers package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to uninstall the package immediately and take necessary precautions to secure their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for pretty-loggers →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall pretty-loggers' and rotate any sensitive information stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

No, there is currently no patched version available for pretty-loggers. The only solution is to remove the package.

Leaving the package installed can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your environment.

Yes, consider using secure logging packages such as winston or bunyan as alternatives to pretty-loggers.

How To Fix

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

npm uninstall pretty-loggers

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