Malicious Code Injection in tuti-tempe16-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75795: Malicious code in tuti-tempe16-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 'tuti-tempe16-breki' is part of a series of malicious npm packages linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores in exchange for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'tuti-tempe16-breki' originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tuti-tempe16-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 measure, avoid using the 'tuti-tempe16-breki' package and monitor your project for any signs of malicious activity. You can also use the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The 'tuti-tempe16-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security and integrity of their projects.
See every vulnerability recorded for tuti-tempe16-breki →
FAQ
The main risk is that it can modify your project's package.json file, potentially leading to unauthorized package publishing and compromising your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have installed 'tuti-tempe16-breki', you should uninstall it immediately using 'npm uninstall tuti-tempe16-breki' and audit your project for any other vulnerabilities.
There are no patches available for 'tuti-tempe16-breki' as it is a malicious package. The best course of action is to remove it from your project.
Regularly audit your npm packages using 'npm audit', keep your dependencies updated, and consider using tools like Vulert for real-time monitoring.
