Malicious Code Injection in gilang-sego36-ruro Package: A Threat to npm Users

gilang-sego36-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103160: Malicious code in gilang-sego36-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The gilang-sego36-ruro package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.

Vulnerability Detail

The vulnerability originates from the malicious design of the gilang-sego36-ruro package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants that can pollute the npm registry, potentially leading to security risks for developers who unknowingly install these packages. The malicious payload can compromise the integrity of applications relying on these packages, making them susceptible to further attacks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall gilang-sego36-ruro

If 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 gilang-sego36-ruro package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies using tools like npm audit to identify and mitigate potential vulnerabilities.

Conclusion

The gilang-sego36-ruro package poses a significant threat due to its malicious code designed to manipulate package metadata and proliferate through the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for gilang-sego36-ruro →

Share this vulnerability

FAQ

The gilang-sego36-ruro package is an npm package involved in a token reward campaign that automates the creation of derivative packages to inflate developer reputation scores.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, which can lead to security vulnerabilities in your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. Visit Vulert Scanner to check if your application is affected without any signup.

You should uninstall the gilang-sego36-ruro package immediately using the command npm uninstall gilang-sego36-ruro and audit your dependencies for any other vulnerabilities.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages effectively.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall gilang-sego36-ruro

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback