Malicious Code Injection in ade-gaplek55-ruro Package

ade-gaplek55-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99139: Malicious code in ade-gaplek55-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 ade-gaplek55-ruro package is part of the npm ecosystem, often utilized in JavaScript applications. It has been identified as part of a broader malicious campaign targeting the npm registry, where packages are created to inflate developer reputation scores through automated publishing scripts. This package specifically has been linked to the tea.xyz token reward campaign, which aims to manipulate the npm registry by generating numerous derivative packages.

Vulnerability Detail

The vulnerability in the ade-gaplek55-ruro package stems from its malicious code designed to modify the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and a compromised developer reputation system. The origin of this vulnerability is traced back to the automated scripts that are part of the malicious campaign.

How To Fix

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

npm uninstall ade-gaplek55-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 workaround, you can temporarily avoid using the ade-gaplek55-ruro package by removing it from your dependencies. You can do this by running the command: npm uninstall ade-gaplek55-ruro. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The ade-gaplek55-ruro package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their applications remain secure from such vulnerabilities.

See every vulnerability recorded for ade-gaplek55-ruro →

Share this vulnerability

FAQ

The ade-gaplek55-ruro package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the pollution of the npm registry and may introduce security risks into your application if the malicious package is used.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

You should uninstall the ade-gaplek55-ruro package immediately and monitor your project for any further vulnerabilities.

Regularly monitor your dependencies using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall ade-gaplek55-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