Malicious Code Injection in kiki-kacang43-ruro Package

kiki-kacang43-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104782: Malicious code in kiki-kacang43-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-kacang43-ruro package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores through automated scripts, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in the kiki-kacang43-ruro package stems from its association with the tea.xyz token reward campaign, which employs malicious scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to pollution of the npm registry. The potential ramifications include compromised project integrity, loss of developer reputation, and exposure to further malicious activities.

How To Fix

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

npm uninstall kiki-kacang43-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-kacang43-ruro package and replace it with a trusted alternative. Additionally, ensure that your package-lock.json is monitored for any changes using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access.

Conclusion

The kiki-kacang43-ruro package poses a significant risk due to its malicious code designed to manipulate npm registry practices. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for kiki-kacang43-ruro →

Share this vulnerability

FAQ

The kiki-kacang43-ruro package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

This vulnerability can compromise your project's integrity, lead to the pollution of the npm registry, and expose your application to further malicious activities.

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

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code.

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

How To Fix

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

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