Critical Malicious Code Vulnerability in adorn Package

adorn Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14109: Malicious code in adorn (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The adorn package is a utility library in the npm ecosystem that provides a set of functions for manipulating and formatting data. It is widely used in various JavaScript applications for its simplicity and efficiency. However, recent findings have revealed that the package contains malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the adorn package, which was introduced in version 0. This code can potentially compromise the security of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The presence of such code is a severe threat, as it can operate unnoticed, affecting the integrity and confidentiality of the application.

How To Fix

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

npm uninstall adorn

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 measure, you can avoid using the adorn package until a secure version is released. Alternatively, consider using other libraries that provide similar functionality without the associated risks.

Conclusion

The adorn package has been identified to contain malicious code, posing a significant security risk to applications. It is crucial to update to a patched version or consider alternative libraries to mitigate potential threats. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for adorn →

Share this vulnerability

FAQ

The adorn package is a utility library in the npm ecosystem designed for data manipulation and formatting in JavaScript applications.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

Yes, you can temporarily avoid using the adorn package or switch to alternative libraries that offer similar functionalities.

Utilize tools like Vulert, which provides real-time monitoring and alerts for open-source vulnerabilities without requiring code access.

How To Fix

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

npm uninstall adorn

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