Malicious Code Injection in putri-mendoan14-breki Package

putri-mendoan14-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-75017: Malicious code in putri-mendoan14-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The putri-mendoan14-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the npm registry, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, potentially compromising the integrity of applications that depend on it.

Vulnerability Detail

The vulnerability stems from the malicious code embedded in the putri-mendoan14-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. The origin of this issue is linked to a token reward campaign that incentivizes the creation of such packages, leading to a significant risk of reputation inflation and potential exploitation of developers' environments.

How To Fix

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

npm uninstall putri-mendoan14-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 temporary measure, you can avoid using the putri-mendoan14-breki package and replace it with a trusted alternative. Always verify the integrity of packages before installation.

Conclusion

The putri-mendoan14-breki package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for putri-mendoan14-breki →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to flood the npm registry with derivative packages.

The malicious code can compromise your application's integrity by modifying package configurations and introducing potentially harmful behavior.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the putri-mendoan14-breki package immediately and review your project's dependencies for any other suspicious packages.

There are no patches available for the putri-mendoan14-breki package as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall putri-mendoan14-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