Malicious Code Injection in sick_wasp-appteadev Package
Summary
MAL-2025-108662: Malicious code in sick_wasp-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 sick_wasp-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 aims to inflate developer reputation scores through the generation of derivative packages. This package, like others in the campaign, is designed to manipulate the npm registry by creating numerous variants of itself with altered metadata.
Vulnerability Detail
The vulnerability in the sick_wasp-appteadev package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names to republish variants continuously. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sick_wasp-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, you can remove the sick_wasp-appteadev package from your project by executing: npm uninstall sick_wasp-appteadev. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The sick_wasp-appteadev package has been compromised with malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities to maintain security and trust in their development environment.
See every vulnerability recorded for sick_wasp-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the injection of malicious code, which may compromise your project's security and integrity.
You should uninstall the package immediately and check for any updates or patches that may be available.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
