Malicious Code Injection in beautiful_roadrunner_z3n Package

beautiful_roadrunner_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99880: Malicious code in beautiful_roadrunner_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 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 beautiful_roadrunner_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to include malicious scripts that can harm developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the beautiful_roadrunner_z3n package stems from its inclusion in a malicious campaign that generates and publishes derivative packages with randomized names. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and continuously republish variants to pollute the npm registry. This can lead to a significant increase in spam packages, affecting the reputation of legitimate developers and potentially introducing security risks into applications that depend on these packages.

How To Fix

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

npm uninstall beautiful_roadrunner_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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check for vulnerabilities in your application without any installation by visiting the Vulert playground at https://vulert.com/scanner.

Conclusion

The beautiful_roadrunner_z3n package has been identified as containing malicious code that can compromise the integrity of the npm registry and affect developers. Immediate action is required to remove this package from any projects to prevent potential security risks.

See every vulnerability recorded for beautiful_roadrunner_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious code.

The vulnerability can lead to the introduction of spam packages and potential security risks, affecting the integrity and reputation of your application.

It is recommended to uninstall the beautiful_roadrunner_z3n package immediately to mitigate any risks.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

How To Fix

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

npm uninstall beautiful_roadrunner_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