Malicious Code Injection in nurul-semur55-breki: A Threat to npm Packages
Summary
MAL-2025-74667: Malicious code in nurul-semur55-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 'nurul-semur55-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. This behavior poses a significant risk to the integrity of the npm registry and the security of applications that depend on these packages.
Vulnerability Detail
The vulnerability in 'nurul-semur55-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 npm ecosystem but also affects developers' ability to trust the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nurul-semur55-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 'nurul-semur55-breki' 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 in real-time.
Conclusion
The 'nurul-semur55-breki' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for nurul-semur55-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed the 'nurul-semur55-breki' package, you should remove it immediately and check for any alternative packages.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time.
Using compromised packages can lead to security breaches, data loss, and a compromised application environment, affecting both developers and end-users.
