Malicious Code Injection in kiki-tempe54-ruro: A Threat to npm Ecosystem

kiki-tempe54-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104818: Malicious code in kiki-tempe54-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package kiki-tempe54-ruro is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been identified as malicious. It is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, ultimately polluting the npm registry.

Vulnerability Detail

The vulnerability in kiki-tempe54-ruro stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to exploit the npm registry, leading to potential security risks such as unauthorized access to sensitive data and the proliferation of untrustworthy packages in the ecosystem.

How To Fix

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

npm uninstall kiki-tempe54-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 measure, you can avoid using the kiki-tempe54-ruro package and monitor your dependencies for any unauthorized changes. Regularly audit your package-lock.json file for any suspicious entries.

Conclusion

The kiki-tempe54-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for kiki-tempe54-ruro →

Share this vulnerability

FAQ

kiki-tempe54-ruro is an npm package that has been identified as malicious, designed to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to unauthorized changes in your project’s dependencies, potentially exposing sensitive data and compromising the integrity of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you find kiki-tempe54-ruro in your project, immediately uninstall it using 'npm uninstall kiki-tempe54-ruro' and review your other dependencies for similar vulnerabilities.

There are no patches available for kiki-tempe54-ruro as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

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