Malicious Code Injection in determined_vulture_z3n Package

determined_vulture_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94008: Malicious code in determined_vulture_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The determined_vulture_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, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers who rely on the integrity of the ecosystem. The malicious scripts included in the package are designed to automate these processes, making it difficult for users to detect the issue.

How To Fix

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

npm uninstall determined_vulture_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 determined_vulture_z3n package and replace it with a trusted alternative that provides similar functionality without the risk of malicious code. Always verify the integrity of packages before including them in your project.

Conclusion

The determined_vulture_z3n package has been identified as containing malicious code that compromises the security of the npm ecosystem. It is crucial for developers to remove this package from their projects and to monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help in maintaining the integrity of your software.

See every vulnerability recorded for determined_vulture_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting other developers relying on the npm ecosystem.

If you have installed the determined_vulture_z3n package, you should uninstall it immediately using the command npm uninstall determined_vulture_z3n.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

Yes, you should look for trusted packages that provide similar functionality without the risk of malicious code. Always verify the source and integrity of packages before use.

How To Fix

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

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