Malicious Code Injection in andi-keripik34-ruro Package - npm Vulnerability

andi-keripik34-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99432: Malicious code in andi-keripik34-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 andi-keripik34-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores. However, it has been identified as containing malicious code that modifies package.json files and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that employs autopublish scripts to manipulate package metadata. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects with untrusted code.

How To Fix

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

npm uninstall andi-keripik34-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 workaround, you can manually check your package-lock.json file for any instances of the andi-keripik34-ruro package and remove it. You can use the following command to uninstall the package: npm uninstall andi-keripik34-ruro.

Conclusion

The andi-keripik34-ruro package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for andi-keripik34-ruro →

Share this vulnerability

FAQ

andi-keripik34-ruro is an npm package associated with a token reward campaign that generates and publishes derivative packages.

The vulnerability can lead to the introduction of untrusted code into your project, potentially compromising its security and integrity.

You should remove the package immediately and check for any other affected packages in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

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

How To Fix

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

npm uninstall andi-keripik34-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