Malicious Code Injection in determined_landfowl_z3n Package

determined_landfowl_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101380: Malicious code in determined_landfowl_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 determined_landfowl_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the determined_landfowl_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects with untrusted code.

How To Fix

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

npm uninstall determined_landfowl_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, avoid using the determined_landfowl_z3n package and monitor your dependencies for any malicious activity. You can also utilize tools like Vulert to check your package-lock.json for vulnerabilities.

Conclusion

The determined_landfowl_z3n package poses a significant risk due to its malicious code that alters package metadata and can lead to npm registry pollution. It is crucial to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for determined_landfowl_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json, remove private flags, and publish untrusted packages, potentially compromising your project.

You can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without requiring any signup.

You should uninstall the determined_landfowl_z3n package immediately and monitor your project for any unusual behavior.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities.

How To Fix

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

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