Malicious Code Injection in hard_mockingbird-appteadev Package
Summary
MAL-2025-103601: Malicious code in hard_mockingbird-appteadev (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 hard_mockingbird-appteadev package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package is particularly vulnerable due to its association with scripts designed to manipulate package metadata and publish unauthorized versions.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the hard_mockingbird-appteadev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The scripts associated with this package are designed to continuously republish variants, which can compromise the integrity of the npm ecosystem and potentially expose applications using these packages to further risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hard_mockingbird-appteadevIf 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, avoid using the hard_mockingbird-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The hard_mockingbird-appteadev package poses a significant risk due to its malicious code designed to manipulate package metadata and publish unauthorized versions. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for hard_mockingbird-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by publishing unauthorized derivative packages.
The vulnerability can lead to the pollution of the npm registry and may expose your application to further risks, including the use of compromised packages.
You should uninstall the hard_mockingbird-appteadev package immediately and check for any alternative packages that can fulfill your requirements.
Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.
You can check your application for vulnerabilities by visiting the Vulert playground at Vulert Scanner without needing to sign up.
