Malicious Code Injection in dreadful_mockingbird-appteadev Package
Summary
MAL-2025-101769: Malicious code in dreadful_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 dreadful_mockingbird-appteadev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, often with randomized names.
Vulnerability Detail
The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for dependency confusion and the introduction of untrusted code into projects that rely on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dreadful_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 workaround, consider using a different, trusted package that fulfills the same functionality as dreadful_mockingbird-appteadev. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation.
Conclusion
The dreadful_mockingbird-appteadev package poses a significant security risk due to its malicious code that modifies project files and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the integrity of your projects.
See every vulnerability recorded for dreadful_mockingbird-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The malicious code modifies your package.json file, potentially introducing untrusted code and leading to security vulnerabilities in your project.
You should remove the dreadful_mockingbird-appteadev package from your project and monitor for any updates or patches that may be released.
You can use tools like Vulert, which monitors your package-lock.json file and alerts you to any open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
