Malicious Code Injection in hendra-semur2-breki: A Threat to npm Packages
Summary
MAL-2025-73409: Malicious code in hendra-semur2-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 'hendra-semur2-breki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability in 'hendra-semur2-breki' originates from its inclusion in a malicious campaign aimed at manipulating the npm ecosystem. The package contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the proliferation of untrustworthy packages in the npm registry, potentially compromising the integrity of applications that depend on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hendra-semur2-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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Ensure that your project does not include 'hendra-semur2-breki' in the package-lock.json. If it is present, remove it and run 'npm install' to regenerate the lock file.
Conclusion
The 'hendra-semur2-breki' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for hendra-semur2-breki →
FAQ
The vulnerability can lead to the proliferation of malicious packages, compromising the integrity of the npm registry and potentially affecting applications that rely on these packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall hendra-semur2-breki' and review your project's dependencies for any other potentially compromised packages.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about updates and patches from package maintainers.
There is no patch available for this specific package as it is considered malicious. The best course of action is to remove it from your project.
