Malicious Code Injection in single_landfowl_z3n Package

single_landfowl_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96602: Malicious code in single_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 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 single_landfowl_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 creation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in the single_landfowl_z3n package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file, removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but can also lead to security risks for developers who unknowingly use these compromised packages. The malicious payload is designed to continuously republish variants, exacerbating the issue.

How To Fix

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

npm uninstall single_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 workaround, you can temporarily avoid using the single_landfowl_z3n package by removing it from your dependencies. You can do this by running the command: npm uninstall single_landfowl_z3n. Additionally, consider using Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The single_landfowl_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for single_landfowl_z3n →

Share this vulnerability

FAQ

The single_landfowl_z3n package is an npm package associated with a token reward campaign that generates derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if you inadvertently use compromised packages.

If you have installed the single_landfowl_z3n package, it is advisable to uninstall it immediately and monitor your project for any potential impacts.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring access to your code or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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