Malicious Code Injection in patria-semur53-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74910: Malicious code in patria-semur53-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 'patria-semur53-breki' is part of a series of malicious npm packages associated with 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, aiming to inflate developer reputation scores for token rewards. The package's functionality is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability stems from the package's malicious code, 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, polluting the npm registry and potentially affecting other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for fraudulent purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall patria-semur53-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 affected 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 'patria-semur53-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. Developers must take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for patria-semur53-breki →
FAQ
The main risk is that it can modify your project's package.json file, leading to the publication of malicious variants and potentially compromising your project's integrity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
You should uninstall the package immediately using 'npm uninstall patria-semur53-breki' and review your project for any other vulnerabilities.
Currently, there are no patches available for the patria-semur53-breki package since it is a malicious package. The best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from trusted sources.
