Malicious Code Injection in static_landfowl_z3n: A Threat to npm Packages
Summary
MAL-2025-96752: Malicious code in static_landfowl_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package static_landfowl_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in static_landfowl_z3n originates from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious code can also affect developers' reputation scores by artificially inflating them through these automated processes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall static_landfowl_z3nIf 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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include static_landfowl_z3n in your package.json or lock file.
Conclusion
The static_landfowl_z3n package poses a significant threat due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial to remove this package and monitor your project for vulnerabilities using tools like Vulert to maintain a secure development environment.
See every vulnerability recorded for static_landfowl_z3n →
FAQ
static_landfowl_z3n is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated package publishing.
The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to a polluted npm registry and affect your project's integrity.
You should immediately remove the package from your project and update your dependencies to ensure your project is secure.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on known vulnerabilities in the npm ecosystem.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
