Malicious Code Injection in budi-keripik94-ruro Package

budi-keripik94-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100154: Malicious code in budi-keripik94-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 budi-keripik94-ruro package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of numerous derivative packages. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly integrate these compromised packages into their projects.

Vulnerability Detail

The vulnerability in the budi-keripik94-ruro package stems from its malicious code, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is part of a broader scheme associated with the tea.xyz token reward campaign, which floods the npm registry with derivative packages to manipulate developer reputation scores. The ramifications include potential exposure to untrusted code, which can lead to security breaches and instability in applications that rely on this package.

How To Fix

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

npm uninstall budi-keripik94-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 budi-keripik94-ruro package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The budi-keripik94-ruro package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure the integrity of their applications.

See every vulnerability recorded for budi-keripik94-ruro →

Share this vulnerability

FAQ

The budi-keripik94-ruro package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the injection of untrusted code into your project, potentially compromising security and stability.

You should uninstall the budi-keripik94-ruro package immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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 budi-keripik94-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