Malicious Code Injection in tuti-miemee34-breki Package
Summary
MAL-2025-75780: Malicious code in tuti-miemee34-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 tuti-miemee34-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and publish harmful variants, thus affecting the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from the package's inclusion in a campaign that generates and publishes numerous derivative packages with randomized names. These packages contain scripts that alter the package.json file by removing private flags and changing version numbers. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry with potentially harmful packages. The malicious payload can lead to security risks for developers and users relying on the npm registry for trusted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tuti-miemee34-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 monitor your package dependencies and avoid using any packages that appear suspicious or are part of the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The tuti-miemee34-breki package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and take immediate action to remove such packages and protect their projects from potential threats.
See every vulnerability recorded for tuti-miemee34-breki →
FAQ
tuti-miemee34-breki is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.
You should immediately uninstall the tuti-miemee34-breki package using the command npm uninstall tuti-miemee34-breki.
Regularly audit your npm packages, keep your dependencies updated, and avoid using packages that seem suspicious.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
