Malicious Code Injection in kiki-gaplek39-ruro Package

kiki-gaplek39-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104778: Malicious code in kiki-gaplek39-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 kiki-gaplek39-ruro package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in its category, is designed to automate the generation and publication of derivative packages, often with randomized names. Its functionality is intended to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that can alter package metadata.

Vulnerability Detail

The vulnerability in the kiki-gaplek39-ruro package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to continuously republish variants with random names, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall kiki-gaplek39-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 kiki-gaplek39-ruro package and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your package dependencies for any signs of malicious activity.

Conclusion

The kiki-gaplek39-ruro package is a clear example of how malicious code can infiltrate the npm ecosystem, posing significant risks to developers. It is essential to remain vigilant, regularly update dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for kiki-gaplek39-ruro →

Share this vulnerability

FAQ

The kiki-gaplek39-ruro package is part of a campaign that generates and publishes derivative npm packages to inflate developer reputation scores for token rewards.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the kiki-gaplek39-ruro package immediately and check your project for any other compromised packages.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities and provide alerts for any issues found.

How To Fix

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

npm uninstall kiki-gaplek39-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