Malicious Code Injection in beautiful_rook_z3n: A Threat to npm Packages

beautiful_rook_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93362: Malicious code in beautiful_rook_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 beautiful_rook_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with randomized names. The goal of this campaign is to inflate developer reputation scores for token rewards, specifically related to the tea.xyz protocol.

Vulnerability Detail

The vulnerability in beautiful_rook_z3n stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign that floods the npm registry with such malicious packages, posing a risk of pollution and potential misuse of the registry.

How To Fix

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

npm uninstall beautiful_rook_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 beautiful_rook_z3n package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes and ensure that your project dependencies are secure.

Conclusion

The beautiful_rook_z3n package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help keep your projects secure.

See every vulnerability recorded for beautiful_rook_z3n →

Share this vulnerability

FAQ

beautiful_rook_z3n is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

The malicious code modifies your package.json file, potentially leading to unauthorized changes and the pollution of the npm registry with derivative packages.

You should uninstall the package immediately using the command 'npm uninstall beautiful_rook_z3n' and check your project for any unauthorized changes.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, you should look for trusted alternatives that provide similar functionality without the associated risks of malicious code.

How To Fix

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

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