Malicious Code Injection in successful_aphid_z3n Package

successful_aphid_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109251: Malicious code in successful_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 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 successful_aphid_z3n package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages typically contain scripts that automatically generate and publish derivative packages, aiming to inflate developer reputation scores for token rewards. However, this behavior poses significant risks to developers and users alike, as it can lead to the proliferation of malicious packages.

Vulnerability Detail

The vulnerability in the successful_aphid_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall successful_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 remove the successful_aphid_z3n package from your project by executing the following command: npm uninstall successful_aphid_z3n. This action will prevent any malicious code from executing in your application until a safe version is released.

Conclusion

The successful_aphid_z3n package contains malicious code that poses significant security risks to applications using it. Developers are urged to remove the package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in identifying and managing such risks effectively.

See every vulnerability recorded for successful_aphid_z3n →

Share this vulnerability

FAQ

The successful_aphid_z3n package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, potentially compromising your application's security.

Currently, there is no specific patched version available for the successful_aphid_z3n package. It is recommended to remove the package until a safe version is released.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

If you are using the successful_aphid_z3n package, it is advisable to uninstall it immediately to prevent any potential security risks.

How To Fix

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

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