Malicious Code Injection in whispering_roundworm_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97355: Malicious code in whispering_roundworm_requirement (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The whispering_roundworm_requirement package is part of the npm ecosystem, typically used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm registry and poses a risk to developers who may unknowingly use it.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also exposes developers to potential security risks as these packages may contain further malicious payloads.

How To Fix

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

npm uninstall whispering_roundworm_requirement

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 remove the whispering_roundworm_requirement package from your project by executing the following command: npm uninstall whispering_roundworm_requirement. This will prevent any malicious code from executing in your application until a safe version is available.

Conclusion

The whispering_roundworm_requirement package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and monitor their applications for any potential threats.

See every vulnerability recorded for whispering_roundworm_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

Yes, you can use Vulert to monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall whispering_roundworm_requirement

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