Malicious Code Injection in rival_roundworm_z3n: A Threat to npm Ecosystem

rival_roundworm_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96384: Malicious code in rival_roundworm_z3n (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'rival_roundworm_z3n' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'rival_roundworm_z3n' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security and reliability of applications relying on these packages. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers seeking token rewards.

How To Fix

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

npm uninstall rival_roundworm_z3n

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 avoid using the 'rival_roundworm_z3n' package and replace it with a trusted alternative. Regularly audit your package-lock.json file to identify and remove any suspicious packages. You can also use tools like Vulert to monitor your dependencies for vulnerabilities in real-time.

Conclusion

The 'rival_roundworm_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. By understanding the nature of this vulnerability and taking proactive steps to remove the affected package, developers can safeguard their applications and maintain the integrity of their dependencies.

See every vulnerability recorded for rival_roundworm_z3n →

Share this vulnerability

FAQ

'rival_roundworm_z3n' is a malicious npm package that is part of a campaign to manipulate the npm registry for token rewards.

This vulnerability can lead to the pollution of the npm registry, potentially introducing insecure and untrusted packages into your application.

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

You should uninstall the 'rival_roundworm_z3n' package immediately and replace it with a trusted alternative.

Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.

How To Fix

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

npm uninstall rival_roundworm_z3n

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