Critical Malicious Code Vulnerability in experimental-utils Package

experimental-utils Updated 12 Jan 2026

Summary

12/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-217: Malicious code in experimental-utils (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 experimental-utils package is an npm library designed for utility functions that aid in experimental projects. It provides various tools and helpers that developers can leverage to streamline their workflows. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the experimental-utils package. This malicious code can fully compromise any computer that has the package installed or running. The ramifications include unauthorized access to sensitive data, such as secrets and keys, which could be exploited by malicious entities. The origin of this vulnerability is linked to a malicious actor who has embedded harmful code in the package, making it a significant threat to users and their systems.

How To Fix

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

npm uninstall experimental-utils

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 rotate all secrets and keys stored on the affected computer from a different, secure computer. This step is vital to mitigate any potential data breaches resulting from the malicious code.

Conclusion

The experimental-utils package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to remove the package and secure their systems. Regular monitoring for vulnerabilities, such as through Vulert, is recommended to maintain software security.

See every vulnerability recorded for experimental-utils →

Share this vulnerability

FAQ

The experimental-utils package is an npm library that provides utility functions for developers working on experimental projects.

You can check if your application is affected by this vulnerability using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

You should immediately remove the experimental-utils package from your system and rotate any sensitive data stored on that computer.

Currently, there is no patched version available. Users are advised to remove the package and take necessary precautions.

Failing to address this vulnerability could lead to unauthorized access to sensitive data, potential data breaches, and full compromise of your system.

How To Fix

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

npm uninstall experimental-utils

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