Critical Malicious Code Vulnerability in pretty-jsonify Package

pretty-jsonify Updated 19 Nov 2025

Summary

18/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190554: Malicious code in pretty-jsonify (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

pretty-jsonify is an npm package designed to format JSON data in a more readable way. It is commonly used in web applications to enhance the presentation of JSON objects. However, this package has been identified to contain malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the pretty-jsonify package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full control of the affected system by an outside entity, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall pretty-jsonify

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, users should ensure that the pretty-jsonify package is uninstalled from their systems. This can be done using the command: npm uninstall pretty-jsonify. Additionally, users should monitor their systems for any unusual activity following the removal of the package.

Conclusion

The discovery of malicious code in the pretty-jsonify package highlights the importance of vigilance when using open-source software. Users must act swiftly to mitigate risks by removing the package and securing their systems. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for pretty-jsonify →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check for vulnerabilities without needing to sign up.

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

Failing to address this vulnerability can lead to unauthorized access to your system and potential data breaches.

While many npm packages are safe, it is crucial to regularly audit and monitor them for vulnerabilities.

How To Fix

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

npm uninstall pretty-jsonify

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