Malicious Code Injection in andi-ikan43-ruro Package

andi-ikan43-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99427: Malicious code in andi-ikan43-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

andi-ikan43-ruro is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. The primary functionality of this package is to participate in the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores through the creation of numerous fake packages.

Vulnerability Detail

The vulnerability in the andi-ikan43-ruro package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.

How To Fix

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

npm uninstall andi-ikan43-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 prevent the package from being used in your project by removing it from your package.json file and running 'npm install' to update your dependencies. Additionally, you can monitor your project for any unauthorized changes to package.json.

Conclusion

The andi-ikan43-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with fake packages. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for andi-ikan43-ruro →

Share this vulnerability

FAQ

andi-ikan43-ruro is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous fake packages.

The vulnerability can lead to unauthorized changes in your package.json file, potentially compromising your project's integrity and security.

You should uninstall the andi-ikan43-ruro package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, 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 andi-ikan43-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