Malicious Code Injection in qualified_aphid-silentdev Package
Summary
MAL-2025-107631: Malicious code in qualified_aphid-silentdev (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 qualified_aphid-silentdev package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores. The vulnerability stems from its association with the tea.xyz token reward campaign, which employs automated scripts to publish derivative packages with altered names and metadata.
Vulnerability Detail
The vulnerability in the qualified_aphid-silentdev package involves the injection of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a campaign that exploits npm's publishing mechanism, potentially allowing attackers to pollute the npm registry and compromise the integrity of dependent projects. The ramifications include the risk of unintentional use of compromised packages, which can lead to security breaches and loss of developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall qualified_aphid-silentdevIf 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 qualified_aphid-silentdev package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The qualified_aphid-silentdev package poses a significant security risk due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package from their projects and adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for qualified_aphid-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.
The malicious code modifies your package.json file, potentially leading to the use of compromised packages and security vulnerabilities in your project.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
You should uninstall the qualified_aphid-silentdev package immediately and replace it with a trusted alternative.
Regularly audit your dependencies, use trusted packages, and keep your software updated to mitigate the risk of vulnerabilities.
