Malicious Code Injection in rifqi-lodeh21-riris Package

rifqi-lodeh21-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90093: Malicious code in rifqi-lodeh21-riris (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 rifqi-lodeh21-riris package is part of the npm ecosystem, typically used for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish variants that can harm the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the rifqi-lodeh21-riris package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, which can lead to pollution of the npm registry and inflate developer reputation scores fraudulently. This behavior poses significant risks, including the potential for dependency confusion and the introduction of malicious code into legitimate projects.

How To Fix

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

npm uninstall rifqi-lodeh21-riris

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 avoid using the rifqi-lodeh21-riris package and replace it with a trusted alternative. Always verify the source and integrity of packages before including them in your project.

Conclusion

The rifqi-lodeh21-riris package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for rifqi-lodeh21-riris →

Share this vulnerability

FAQ

The rifqi-lodeh21-riris package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the introduction of malicious code into your project and can compromise the integrity of your dependencies.

You should uninstall the rifqi-lodeh21-riris package immediately and check your project for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall rifqi-lodeh21-riris

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