Malicious Code Injection in fadhil-ikan48-ruro Package: A Threat to npm Users

fadhil-ikan48-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102469: Malicious code in fadhil-ikan48-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The fadhil-ikan48-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to developers and users alike.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the fadhil-ikan48-ruro package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, often themed around Indonesian culture. The malicious scripts continuously republish these variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include the risk of unintentional installation of these malicious packages by developers, leading to further exploitation.

How To Fix

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

npm uninstall fadhil-ikan48-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 fadhil-ikan48-ruro package and any other packages that may be associated with the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially malicious packages.

Conclusion

The fadhil-ikan48-ruro package poses a significant threat to npm users due to its malicious code designed to exploit the npm registry. It is crucial to remove this package and any associated dependencies to protect your projects. Regular audits and the use of tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for fadhil-ikan48-ruro →

Share this vulnerability

FAQ

The impact includes the risk of unintentional installation of malicious packages, which can compromise your project's security and integrity.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected.

Immediately uninstall the fadhil-ikan48-ruro package using npm uninstall fadhil-ikan48-ruro and audit your dependencies for any other malicious packages.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities without requiring access to your code.

It is recommended to check for vulnerabilities regularly, especially after adding new packages or updating existing ones.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall fadhil-ikan48-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