Malicious Code Injection in rifqi-kupang75-ruro Package

rifqi-kupang75-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108082: Malicious code in rifqi-kupang75-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The rifqi-kupang75-ruro package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that includes scripts like auto.js and autopublish.js. These scripts are designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. This not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious behavior poses a significant risk as it can lead to the installation of compromised packages by unsuspecting users.

How To Fix

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

npm uninstall rifqi-kupang75-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 monitor your project for any instances of the rifqi-kupang75-ruro package and remove it immediately. Additionally, consider using tools like Vulert, which can help you monitor and alert for open-source vulnerabilities in your software without requiring access to the code or installation. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner.

Conclusion

The rifqi-kupang75-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor for any similar vulnerabilities using tools like Vulert to ensure the security of your software.

See every vulnerability recorded for rifqi-kupang75-ruro →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns that has been identified as containing malicious code.

The malicious code modifies your package.json file and floods the npm registry with unwanted variants, potentially leading to the installation of compromised packages.

You should uninstall the rifqi-kupang75-ruro package immediately and monitor your project for any further instances of malicious packages.

Using tools like Vulert can help you monitor for vulnerabilities in real-time and alert you to any issues without needing to access your code.

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 rifqi-kupang75-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