Malicious Code Injection in putri-mieayam35-breki Package
Summary
MAL-2025-75024: Malicious code in putri-mieayam35-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The putri-mieayam35-breki package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and repackages itself, posing a significant risk to developers and users.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the putri-mieayam35-breki package, which includes scripts that automatically alter the package.json file to remove private flags and change version numbers. This allows the package to continuously republish itself under different names, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include the risk of executing malicious code and compromising the integrity of projects that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-mieayam35-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, avoid using the putri-mieayam35-breki package and any packages that depend on it. Regularly audit your dependencies to ensure that no malicious packages are included in your project.
Conclusion
The putri-mieayam35-breki package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to remove this package from their projects and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for putri-mieayam35-breki →
FAQ
It is an npm package associated with a token reward campaign that has been identified to contain malicious code.
The vulnerability can lead to the installation of compromised packages, which may execute malicious code and compromise your project's security.
You should uninstall the putri-mieayam35-breki package immediately and check your project for any other affected packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
