Malicious Code Injection in hadi-bakso40-ruro Package - npm Vulnerability

hadi-bakso40-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103436: Malicious code in hadi-bakso40-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 hadi-bakso40-ruro package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. The malicious nature of this package compromises its integrity and poses significant risks to users who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also exposes users to potential security risks, including unauthorized access and data breaches.

How To Fix

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

npm uninstall hadi-bakso40-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 workaround, you can avoid using the hadi-bakso40-ruro package and look for alternative packages that serve similar functionalities without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The hadi-bakso40-ruro package poses significant risks due to its malicious code designed to manipulate package metadata and pollute the npm registry. Users are advised to uninstall this package immediately and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for hadi-bakso40-ruro →

Share this vulnerability

FAQ

The hadi-bakso40-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.

If you have installed the hadi-bakso40-ruro package, you should uninstall it immediately using 'npm uninstall hadi-bakso40-ruro' and look for secure alternatives.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

While specific alternatives depend on your project's requirements, always search for well-reviewed and actively maintained packages in the npm registry.

How To Fix

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

npm uninstall hadi-bakso40-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