Malicious Code Injection in putra-mangut56-breki: A Threat to npm Packages
Summary
MAL-2025-74939: Malicious code in putra-mangut56-breki (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-mangut56-breki' 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. The primary function of such packages is to manipulate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'putra-mangut56-breki' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and potential security risks for users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-mangut56-brekiIf 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 'putra-mangut56-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'putra-mangut56-breki' package poses significant risks due to its malicious code designed to manipulate npm registry data. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying vigilant and proactive can help maintain the security and integrity of your applications.
See every vulnerability recorded for putra-mangut56-breki →
FAQ
The main risk is the potential for malicious code to compromise your application, leading to security vulnerabilities and damage to your developer reputation.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed 'putra-mangut56-breki', you should uninstall it immediately using 'npm uninstall putra-mangut56-breki' and look for alternative packages.
Yes, tools like Vulert can monitor your package-lock.json file in real-time for open-source vulnerabilities, alerting you to any issues.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
