Malicious Code Injection in effective_landfowl_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94184: Malicious code in effective_landfowl_requirement (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 effective_landfowl_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the npm registry, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in the effective_landfowl_requirement package stems from its association with a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry and can lead to the unintentional installation of compromised packages by developers. The malicious scripts, such as auto.js and autopublish.js, are designed to automatically publish these harmful packages, making it difficult for developers to identify and avoid them.

How To Fix

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

npm uninstall effective_landfowl_requirement

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 effective_landfowl_requirement package until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The effective_landfowl_requirement package poses a significant security risk due to its malicious code that alters package metadata and publishes harmful variants. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.

See every vulnerability recorded for effective_landfowl_requirement →

Share this vulnerability

FAQ

It is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.

The vulnerability can lead to the installation of malicious packages, compromising your project's integrity and security.

You should immediately update the package to the latest version or remove it from your project.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall effective_landfowl_requirement

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