Malicious Code Injection in passing_sturgeon-appteadev Package
Summary
MAL-2025-106931: Malicious code in passing_sturgeon-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 passing_sturgeon-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 publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the package's involvement in a token reward campaign that utilizes malicious scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses risks of dependency confusion and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall passing_sturgeon-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 passing_sturgeon-appteadev package from your project until a secure version is available. Use the following command to uninstall it: npm uninstall passing_sturgeon-appteadev.
Conclusion
The passing_sturgeon-appteadev package has been identified as containing malicious code that can compromise the security of applications relying on it. It is crucial to take immediate action by updating or removing the package to mitigate potential risks.
See every vulnerability recorded for passing_sturgeon-appteadev →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, leading to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Using this package can lead to dependency confusion, potential exploitation, and overall security risks due to its malicious behavior.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is available.
