Malicious Code Injection in hadianto-soto98-ruro: A Threat to npm Ecosystem

hadianto-soto98-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103516: Malicious code in hadianto-soto98-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 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 package 'hadianto-soto98-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to inflate developer reputation scores through automated scripts that generate and publish derivative packages with randomized names.

Vulnerability Detail

The vulnerability in 'hadianto-soto98-ruro' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry. This behavior is indicative of a broader trend where malicious actors exploit the npm ecosystem for token rewards, potentially compromising the integrity of the registry and affecting developers relying on these packages.

How To Fix

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

npm uninstall hadianto-soto98-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 measure, you can avoid using the 'hadianto-soto98-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'hadianto-soto98-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant, regularly update their dependencies, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for hadianto-soto98-ruro →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing further security risks.

You should uninstall the package immediately using 'npm uninstall hadianto-soto98-ruro' and check your project for any other potentially malicious dependencies.

Yes, regularly update your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities in real-time.

Vulert is a tool that monitors open-source vulnerabilities in your software using just the package-lock.json file. It alerts you in real-time for any vulnerabilities, helping you maintain the security of your applications.

How To Fix

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

npm uninstall hadianto-soto98-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