Malicious Code Injection in Successive Prawn Dumbs Package
Summary
MAL-2025-109265: Malicious code in successive_prawn_dumbs (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 'successive_prawn_dumbs' package is part of the npm ecosystem, often used in JavaScript applications. 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, like others in the campaign, is designed to manipulate the npm registry by creating numerous variants with randomized names.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can compromise the integrity of applications relying on this package, potentially exposing them to further attacks or instability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall successive_prawn_dumbsIf 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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that you do not install any packages that depend on 'successive_prawn_dumbs'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'successive_prawn_dumbs' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for successive_prawn_dumbs →
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 pollution of the npm registry, potentially compromising the integrity and security of your application.
You should uninstall the package immediately and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
