Malicious Code Injection in kiki-pisang8-ruro Package

kiki-pisang8-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104806: Malicious code in kiki-pisang8-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 Your last release was probably never penetration tested 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-pisang8-ruro package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the kiki-pisang8-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random Indonesian-themed package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who inadvertently use these packages.

How To Fix

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

npm uninstall kiki-pisang8-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, avoid using the kiki-pisang8-ruro package and monitor your project for any dependencies that may have been affected by this malicious package. You can also use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected, you can visit the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The kiki-pisang8-ruro package poses a significant risk due to its malicious code that alters project configurations and pollutes the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for kiki-pisang8-ruro →

Share this vulnerability

FAQ

The kiki-pisang8-ruro package is an npm package that is part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry with unwanted packages.

If you have installed the kiki-pisang8-ruro package, you should uninstall it immediately using npm uninstall kiki-pisang8-ruro.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. Visit Vulert Scanner to check your application.

Currently, there is no patched version of the kiki-pisang8-ruro package. The best course of action is to uninstall it and monitor for updates.

How To Fix

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

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