Malicious Code Detected in extraction-test-javascript-utilities Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20106: Malicious code in extraction-test-javascript-utilities (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 extraction-test-javascript-utilities package is an npm library designed for utility functions in JavaScript extraction processes. It is commonly used in various applications for its ease of use and functionality. However, this package has been found to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the extraction-test-javascript-utilities package stems from the inclusion of malicious code that can compromise the security of applications relying on it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been flagged by security researchers, indicating a serious threat to users of this package.

How To Fix

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

npm uninstall extraction-test-javascript-utilities

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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The extraction-test-javascript-utilities package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Users are advised to uninstall the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your projects.

See every vulnerability recorded for extraction-test-javascript-utilities →

Share this vulnerability

FAQ

It is an npm library used for utility functions in JavaScript extraction processes.

The malicious code can lead to unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no patched version available. It is recommended to uninstall the package until a fix is released.

Uninstall the package immediately and consider using alternative libraries that do not have known vulnerabilities.

How To Fix

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

npm uninstall extraction-test-javascript-utilities

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