Malicious Code Injection in poor_puffin-appteadev Package
Summary
MAL-2025-107140: Malicious code in poor_puffin-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 poor_puffin-appteadev package is part of the npm ecosystem, primarily used for developing applications. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish variants that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from the package being associated with a campaign that generates and publishes derivative packages with randomized names. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to 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 poor_puffin-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 avoid using the poor_puffin-appteadev package and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The poor_puffin-appteadev package poses a significant risk due to its association with malicious activities in the npm ecosystem. It is crucial for developers to remove this package and stay vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.
See every vulnerability recorded for poor_puffin-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with harmful packages.
Using this package can lead to security breaches, as it modifies package metadata and republish variants that may be harmful.
You should remove the package from your project and monitor for any updates or patches that may be released.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
