Malicious Code Injection in assistant_ape_z3n Package

assistant_ape_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99637: Malicious code in assistant_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The assistant_ape_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards but has been compromised to include malicious scripts that manipulate package metadata. Its primary function is to assist developers in managing their npm packages, but due to its vulnerabilities, it poses significant risks to users.

Vulnerability Detail

The vulnerability in the assistant_ape_z3n package originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall assistant_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 workaround, users can avoid using the assistant_ape_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, users can monitor their package-lock.json file for any unauthorized changes.

Conclusion

The assistant_ape_z3n package has been identified as containing malicious code that can compromise the integrity of npm projects. Users are advised to update or remove the package to protect their applications from potential security threats. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for assistant_ape_z3n →

Share this vulnerability

FAQ

The assistant_ape_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to assist developers in managing their npm packages.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially exposing your project to security risks and affecting the integrity of your dependencies.

If you have installed the assistant_ape_z3n package, it is crucial to update it to the latest version or remove it from your project to mitigate the risks associated with this vulnerability.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Vulert uses your package-lock.json file to alert you of any vulnerabilities without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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