Malicious Code Injection in putra-donat8-apidev: A Threat to npm Ecosystem
Summary
MAL-2025-89555: Malicious code in putra-donat8-apidev (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 package 'putra-donat8-apidev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in 'putra-donat8-apidev' stems from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-donat8-apidevIf 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 'putra-donat8-apidev' package from your project by executing: 'npm uninstall putra-donat8-apidev'. This will prevent any malicious code from executing until a proper fix is applied.
Conclusion
The 'putra-donat8-apidev' package poses a significant threat due to its malicious code that manipulates npm package metadata. It is crucial for developers to stay vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for putra-donat8-apidev →
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 your software. By checking your package-lock.json file, Vulert can help you identify affected packages.
Using this package can lead to security risks such as unauthorized access to your project, reputation damage, and potential legal implications due to the malicious behavior.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Additionally, only use trusted packages from reputable sources.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
