Malicious Code Injection in inner_rook_z3n Package

inner_rook_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95032: Malicious code in inner_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 inner_rook_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign associated with the tea.xyz token reward system. Its primary function is to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, this functionality has been exploited to introduce malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the inner_rook_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with altered metadata. This includes removing private flags from package.json, changing version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers who rely on the integrity of the packages they use.

How To Fix

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

npm uninstall inner_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, avoid using the inner_rook_z3n package and monitor your project's dependencies for any signs of malicious activity. Regularly check your package-lock.json file for any unexpected changes.

Conclusion

The inner_rook_z3n package has been identified as a vector for malicious code injection, primarily due to its association with a campaign that manipulates npm's publishing mechanisms. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their projects.

See every vulnerability recorded for inner_rook_z3n →

Share this vulnerability

FAQ

The inner_rook_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic publication of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and compromising its security.

If you have installed the inner_rook_z3n package, it is recommended to uninstall it immediately using the command: npm uninstall inner_rook_z3n.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check for vulnerabilities without any signup at the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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