Critical Malicious Code Vulnerability in unadapter Package

unadapter Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191439: Malicious code in unadapter (npm). Affects unadapter versions 0.1.3. 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 unadapter package is an npm library designed for various utility functions in JavaScript applications. It is widely used for its simplicity and effectiveness in adapting data structures. However, it has recently been compromised, leading to severe security vulnerabilities that can affect any system using this package.

Vulnerability Detail

The vulnerability originates from a malicious code injection in version 0.1.3 of the unadapter package, linked to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials, publishing them to GitHub, and can propagate itself to other npm packages owned by the user. The malicious payload may also destroy the user's home directory, leading to a complete compromise of the affected system.

How To Fix

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

npm uninstall unadapter

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 consider isolating their development environments and using containerization to prevent the spread of malicious code. Additionally, monitoring tools like Vulert can be employed to track vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The unadapter package has been compromised, leading to a critical vulnerability that can severely impact systems using it. Immediate action is required to remove the package and secure any exposed credentials. Utilizing monitoring tools like Vulert can help in identifying and managing such vulnerabilities in the future.

See every vulnerability recorded for unadapter →

Share this vulnerability

FAQ

The unadapter package is an npm library used for utility functions in JavaScript applications, allowing developers to easily adapt data structures.

The malicious code can steal sensitive tokens and credentials, publish them to GitHub, and potentially destroy your home directory, leading to a complete system compromise.

You should immediately remove the unadapter package and rotate all secrets and keys stored on your system from a secure environment.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall unadapter

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