Malicious Code Injection in kiki-serimuka63-ruro Package

kiki-serimuka63-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104811: Malicious code in kiki-serimuka63-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-serimuka63-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the kiki-serimuka63-ruro package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The impact includes compromised developer reputation and the risk of unintentional use of these malicious packages in other projects.

How To Fix

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

npm uninstall kiki-serimuka63-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-serimuka63-ruro package and any packages that depend on it. Regularly monitor your package-lock.json file for any unauthorized changes or additions. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The kiki-serimuka63-ruro package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from potential threats.

See every vulnerability recorded for kiki-serimuka63-ruro →

Share this vulnerability

FAQ

The kiki-serimuka63-ruro package is an npm package associated with a token reward campaign that automates the generation of derivative packages.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security risks and pollution of the npm registry.

You should uninstall the kiki-serimuka63-ruro package immediately and check for any dependencies that may be affected.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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