Malicious Code Injection in riyanto-115 Package: A Threat to npm Ecosystem

riyanto-115 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165099: Malicious code in riyanto-115 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The riyanto-115 package is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can lead to reputation inflation for developers seeking rewards. However, its malicious nature poses significant risks to the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the riyanto-115 package, which contains malicious scripts that modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior not only compromises the security of the affected packages but also undermines the trustworthiness of the npm ecosystem as a whole.

How To Fix

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

npm uninstall riyanto-115

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 installation of the riyanto-115 package by using the following command to uninstall it: npm uninstall riyanto-115. Additionally, consider using npm audit to check for other vulnerabilities in your project.

Conclusion

The riyanto-115 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package configurations and floods the registry with unwanted variants. It is essential to take immediate action to remove this package and monitor your projects for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for riyanto-115 →

Share this vulnerability

FAQ

The riyanto-115 package is part of a malicious campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can compromise the integrity of your project by introducing malicious code that alters package configurations and can lead to further exploitation.

You should immediately uninstall the riyanto-115 package and check your project for any other vulnerabilities using npm audit.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the riyanto-115 vulnerability without any signup.

How To Fix

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

npm uninstall riyanto-115

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