Malicious Code Vulnerability in round_ape_z3n Package

round_ape_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108210: Malicious code in round_ape_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The round_ape_z3n package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages designed to manipulate developer reputation scores. This vulnerability poses significant risks to developers and users relying on this package.

Vulnerability Detail

The vulnerability originates from the round_ape_z3n package, which is linked to a broader malicious activity involving the tea.xyz token reward campaign. The package contains scripts that automatically modify package.json files to remove private flags, change version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of applications that depend on this package.

How To Fix

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

npm uninstall round_ape_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 measure, you can avoid using the round_ape_z3n package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package management practices to monitor and control the packages used in your application.

Conclusion

The round_ape_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry integrity. It is essential for developers to remove this package and monitor their applications for vulnerabilities to maintain security and reliability.

See every vulnerability recorded for round_ape_z3n →

Share this vulnerability

FAQ

The round_ape_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of applications that depend on the affected package.

You should remove the round_ape_z3n package from your project and monitor for any updates or patches that may be released.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.

Regularly audit your dependencies, update packages to their latest versions, and utilize tools like Vulert to monitor for vulnerabilities in your open-source software.

How To Fix

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

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