Malicious Code Injection in wibowo-keripik18-ruro Package

wibowo-keripik18-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110856: Malicious code in wibowo-keripik18-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wibowo-keripik18-ruro package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package is associated with a token reward campaign that has been flooding the npm registry with malicious packages. Its primary function is to facilitate the distribution of software, but it has been compromised to include harmful scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the wibowo-keripik18-ruro package, which contains malicious code designed to alter the package.json file. This code removes private flags, changes version numbers, and generates random package names, leading to the automatic publication of derivative packages. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and damage to the reputation of legitimate developers.

How To Fix

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

npm uninstall wibowo-keripik18-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 wibowo-keripik18-ruro package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The wibowo-keripik18-ruro package contains malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to remove this package and monitor your projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for wibowo-keripik18-ruro →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious code, primarily associated with a token reward campaign.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately using npm uninstall wibowo-keripik18-ruro and monitor your project for any further vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

Yes, Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time.

How To Fix

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

npm uninstall wibowo-keripik18-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