Malicious Code Injection in everyday_aphid_requirement Package
Summary
MAL-2025-94314: Malicious code in everyday_aphid_requirement (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
Background
The everyday_aphid_requirement package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate certain functionalities, but it has been compromised as part of a broader malicious campaign targeting npm packages. This vulnerability stems from the package's involvement in the tea.xyz token reward scheme, which has led to the proliferation of malicious scripts that manipulate package metadata and publish unauthorized derivatives.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall everyday_aphid_requirementIf 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 everyday_aphid_requirement package until a secure version is released. Additionally, you may want to audit your npm packages using the command npm audit to identify any other potential vulnerabilities.
Conclusion
The everyday_aphid_requirement package has been identified as a vector for malicious code injection due to its involvement in a fraudulent npm campaign. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications from potential threats.
See every vulnerability recorded for everyday_aphid_requirement →
FAQ
It is an npm package that has been compromised as part of a malicious campaign, leading to the injection of harmful scripts.
The vulnerability can lead to unauthorized modifications of your package.json file and the potential introduction of malicious code into your application.
You should immediately update the package to a patched version or remove it from your project to mitigate the risk.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access 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.
