Malicious Code Injection in gilang-tempe98-ruro: npm Package Vulnerability
Summary
MAL-2025-103169: Malicious code in gilang-tempe98-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 gilang-tempe98-ruro package is part of a series of npm packages that have been identified as part of a malicious campaign aimed at inflating developer reputation scores for token rewards. These packages typically include scripts that automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in the gilang-tempe98-ruro package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to the automatic publication of numerous variants, which can clutter the npm registry and potentially introduce security risks to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gilang-tempe98-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 temporary workaround, you can prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The gilang-tempe98-ruro package poses a significant security risk due to its malicious code that modifies package metadata and publishes unwanted variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for gilang-tempe98-ruro →
FAQ
gilang-tempe98-ruro is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and cluttering your project's dependency tree with unwanted packages.
You should remove the gilang-tempe98-ruro package from your project and monitor for any updates or patches that may address this vulnerability.
Yes, Vulert can be used to monitor your project for open-source vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
Currently, there is no specific patched version available for the gilang-tempe98-ruro package. It is advisable to remove the package until a secure version is released.
