Malicious Code Injection in advanced_asp_z3n Package - npm Vulnerability

advanced_asp_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93144: Malicious code in advanced_asp_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 advanced_asp_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious scripts within the advanced_asp_z3n package. These scripts are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the package but also contributes to the pollution of the npm registry, potentially affecting developers' reputations and the overall ecosystem.

How To Fix

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

npm uninstall advanced_asp_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 workaround, you can temporarily avoid using the advanced_asp_z3n package in your project. If you have dependencies relying on it, consider replacing them with alternative packages that do not exhibit malicious behavior.

Conclusion

The advanced_asp_z3n package has been identified as malicious, posing significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for advanced_asp_z3n →

Share this vulnerability

FAQ

The advanced_asp_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially affecting your application's functionality.

You should remove the advanced_asp_z3n package from your project and check for any dependencies that may rely on it.

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

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you include in your project for any known issues.

How To Fix

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

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