Malicious Code Injection in bambang-lapis26-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-99771: Malicious code in bambang-lapis26-ruro (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 'bambang-lapis26-ruro' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores. Its primary functionality revolves around publishing random packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'bambang-lapis26-ruro' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, thereby continuously republishing variants to the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly incorporate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bambang-lapis26-ruroIf 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 workaround, you can monitor your project's dependencies using tools like Vulert. By utilizing Vulert's playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without needing to sign up. This tool analyzes your package-lock.json file to alert you in real-time about any open-source vulnerabilities.
Conclusion
The 'bambang-lapis26-ruro' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repackages itself. Developers are advised to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Staying informed and proactive is essential to maintaining secure software environments.
See every vulnerability recorded for bambang-lapis26-ruro →
FAQ
The main issue is that it contains malicious code that modifies package.json files and repackages itself under random names, leading to npm registry pollution.
You can use Vulert's playground to analyze your package-lock.json file for vulnerabilities related to the bambang-lapis26-ruro package.
You should uninstall the package immediately using the command 'npm uninstall bambang-lapis26-ruro' to mitigate any risks.
Currently, there are no patched versions available for the bambang-lapis26-ruro package, so removal is the best course of action.
Vulert uses your package-lock.json file to monitor and alert you in real-time for any open-source vulnerabilities, making it easier to maintain secure applications.
