Malicious Code Injection in putri-poke22: A Threat to npm Packages
Summary
MAL-2025-164581: Malicious code in putri-poke22 (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 'putri-poke22' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like others in its category, is intended to inflate developer reputation scores for rewards associated with the tea protocol. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'putri-poke22' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry and potentially harming developers who rely on the integrity of npm packages. The malicious code is part of a broader trend of packages flooding the npm ecosystem with harmful scripts.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-poke22If 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 'putri-poke22' package and monitor your project for any unintended dependencies that may have been introduced. Use the following command to check for vulnerabilities in your project: 'npm audit'.
Conclusion
The 'putri-poke22' package poses a significant risk due to its malicious code that alters project files and pollutes the npm registry. It is crucial for developers to remove this package and stay vigilant about their dependencies. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for putri-poke22 →
FAQ
The malicious code can lead to the modification of your package.json file, removal of private flags, and the generation of random package names, which can compromise the integrity of your project.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can also check your project using the Vulert playground at Vulert Scanner.
There is no patch available for putri-poke22 as it is recommended to uninstall the package entirely to mitigate the risk.
You should immediately uninstall the package using 'npm uninstall putri-poke22' and review your project for any other potentially harmful dependencies.
Regularly audit your dependencies using 'npm audit', keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities.
