Malicious Code Injection in mulyono-lodeh71-breki Package - npm Vulnerability

mulyono-lodeh71-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74467: Malicious code in mulyono-lodeh71-breki (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 mulyono-lodeh71-breki package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the mulyono-lodeh71-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall mulyono-lodeh71-breki

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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor dependencies. You can also use the following command to audit your project for vulnerabilities: npm audit.

Conclusion

The mulyono-lodeh71-breki package contains malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take necessary actions to remove the affected package, and utilize tools like Vulert to monitor their projects for potential threats.

See every vulnerability recorded for mulyono-lodeh71-breki →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

The malicious code modifies your package.json file and can lead to the installation of compromised packages, risking your project's security.

You should remove the mulyono-lodeh71-breki package from your project and check for any updates or patches.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring an account.

How To Fix

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

npm uninstall mulyono-lodeh71-breki

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