Malicious Code Injection in diverse_aphid_z3n Package

diverse_aphid_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94076: Malicious code in diverse_aphid_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The diverse_aphid_z3n package is part of the npm ecosystem and has been associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the diverse_aphid_z3n package, which includes scripts that modify package.json files to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially affecting other developers and users relying on the integrity of npm packages. The malicious payload can cause significant disruption and undermine trust in the npm ecosystem.

How To Fix

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

npm uninstall diverse_aphid_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 diverse_aphid_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The diverse_aphid_z3n package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. Immediate action is required to remove this package and safeguard your projects from potential harm. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

See every vulnerability recorded for diverse_aphid_z3n →

Share this vulnerability

FAQ

The diverse_aphid_z3n package is an npm package linked to a token reward campaign that has been identified to contain malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the republishing of harmful variants, potentially compromising your project's integrity.

You should immediately remove the diverse_aphid_z3n package from your project and monitor for any unauthorized changes in your package-lock.json.

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.

Regularly audit your dependencies, use tools like Vulert to monitor vulnerabilities, and stay updated with the latest security patches for your packages.

How To Fix

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

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