Malicious Code Injection in known_rook_z3n Package

known_rook_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95179: Malicious code in known_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The known_rook_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This package has been identified as part of a scheme that generates and publishes derivative packages with the intent to inflate developer reputation scores for token rewards, making it a target for exploitation.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the known_rook_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names, which can lead to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently introduce vulnerabilities into their applications.

How To Fix

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

npm uninstall known_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 known_rook_z3n package and any other packages that are part of the tea.xyz token reward campaign. Additionally, you can monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The known_rook_z3n package has been identified as containing malicious code that can compromise your project. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your software.

See every vulnerability recorded for known_rook_z3n →

Share this vulnerability

FAQ

The known_rook_z3n package is an npm package involved in JavaScript development, often linked to token reward campaigns that can lead to the creation of malicious packages.

The malicious code can modify your package.json file, remove private flags, and generate random package names, potentially leading to security vulnerabilities in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

If you cannot update the known_rook_z3n package, it is advisable to remove it from your project and look for alternative packages that do not have known vulnerabilities.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using packages from untrusted sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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