Malicious Code Injection in gilang-ragi29-ruro Package

gilang-ragi29-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103154: Malicious code in gilang-ragi29-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gilang-ragi29-ruro package is part of the npm ecosystem, typically used for various JavaScript applications. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the gilang-ragi29-ruro package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and changes version numbers. It generates random package names and continuously republishes variants, which can lead to a compromised npm registry and potential security risks for developers using these packages. This behavior is indicative of a broader issue where malicious actors exploit the npm ecosystem for token rewards, thereby undermining trust in the platform.

How To Fix

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

npm uninstall gilang-ragi29-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-ragi29-ruro package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and source of packages before including them in your project.

Conclusion

The gilang-ragi29-ruro package poses a significant risk due to its involvement in a malicious campaign that modifies package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for gilang-ragi29-ruro →

Share this vulnerability

FAQ

The gilang-ragi29-ruro package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

This vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and compromising its security.

If you have installed the gilang-ragi29-ruro package, you should uninstall it immediately using the command npm uninstall gilang-ragi29-ruro.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative packages that provide similar functionality but have a verified and trusted reputation in the npm ecosystem.

How To Fix

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

npm uninstall gilang-ragi29-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