Malicious Code in daily_roundworm_0xrequest: A Threat to npm Users

daily_roundworm_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101189: Malicious code in daily_roundworm_0xrequest (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package daily_roundworm_0xrequest is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to alter the package.json file, compromising the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability originates from the daily_roundworm_0xrequest package, which contains malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a compromised development environment, inflated reputation scores, and potential security risks for projects relying on affected packages.

How To Fix

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

npm uninstall daily_roundworm_0xrequest

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 the npm audit command to identify vulnerabilities in your project. Additionally, consider using npm ci to install only the dependencies listed in your package-lock.json, which can help mitigate the risk of inadvertently installing compromised packages.

Conclusion

The daily_roundworm_0xrequest package poses a significant threat to npm users by introducing malicious code that alters project files and inflates reputation scores. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for daily_roundworm_0xrequest →

Share this vulnerability

FAQ

It is a malicious npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.

The vulnerability can compromise your project's integrity by modifying critical files and introducing potentially harmful code.

You should remove the package immediately and check for any changes made to your package.json file.

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 in your application without any signup.

How To Fix

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

npm uninstall daily_roundworm_0xrequest

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