Malicious Code Injection in kurniawan-bakwan97-riris Package

kurniawan-bakwan97-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-87565: Malicious code in kurniawan-bakwan97-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 kurniawan-bakwan97-riris package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It contains scripts designed to automatically publish derivative packages with altered metadata, which can lead to significant issues in the npm registry.

Vulnerability Detail

The vulnerability in the kurniawan-bakwan97-riris package originates from its association with a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for applications relying on this package, and damage to developer reputations.

How To Fix

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

npm uninstall kurniawan-bakwan97-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 workaround, you can temporarily avoid using the kurniawan-bakwan97-riris package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project using tools like Vulert, which can alert you to vulnerabilities in your dependencies.

Conclusion

The kurniawan-bakwan97-riris package poses a significant risk due to its malicious code that alters package metadata and republishing behavior. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for kurniawan-bakwan97-riris →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and potential security risks for applications that depend on this package.

You should uninstall the package immediately and look for secure alternatives.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall kurniawan-bakwan97-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