Malicious Code Injection in virtualize-kernel-string-cluster-mu Package

Summary

13/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190162: Malicious code in virtualize-kernel-string-cluster-mu (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The virtualize-kernel-string-cluster-mu package is part of the npm ecosystem, typically used for virtualizing kernel string clusters. It is designed to facilitate certain functionalities within JavaScript applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, affecting developers and users alike.

Vulnerability Detail

The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, leading to pollution of the npm registry. The ramifications include compromised developer reputation scores and potential security risks for applications relying on this package.

How To Fix

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

npm uninstall virtualize-kernel-string-cluster-mu

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, you can prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include the virtualize-kernel-string-cluster-mu package.

Conclusion

The virtualize-kernel-string-cluster-mu package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to uninstall this package and monitor for any updates or patches. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for virtualize-kernel-string-cluster-mu →

Share this vulnerability

FAQ

The malicious code can lead to the automatic generation of harmful packages, affecting the integrity of the npm registry and potentially compromising applications that depend on it.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the virtualize-kernel-string-cluster-mu package, you should uninstall it immediately using 'npm uninstall virtualize-kernel-string-cluster-mu'.

Currently, there are no specific patches for this vulnerability, but it is advisable to monitor the npm registry for any updates or patched versions.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall virtualize-kernel-string-cluster-mu

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