Malicious Code Injection in putri-bakwan98-breki Package

putri-bakwan98-breki Updated 12 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-74964: Malicious code in putri-bakwan98-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-bakwan98-breki package is part of the npm ecosystem, typically used for JavaScript development. It has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, leading to potential misuse and pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the putri-bakwan98-breki package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, thereby polluting the npm registry and compromising the integrity of the ecosystem. Developers using this package may unknowingly contribute to the spread of malicious code, leading to security risks in their applications.

How To Fix

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

npm uninstall putri-bakwan98-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 workaround, you can avoid using the putri-bakwan98-breki 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.

Conclusion

The putri-bakwan98-breki package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for putri-bakwan98-breki →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit the Vulert playground to check your application without needing to sign up.

Using this package can lead to the introduction of malicious code into your application, potentially compromising security and integrity.

Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in your open-source packages.

Remove the putri-bakwan98-breki package immediately and consider replacing it with a safer alternative. Also, review your project for any potential impacts.

How To Fix

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

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