Malicious Code Injection in putri-bika21-miaww Package

putri-bika21-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89632: Malicious code in putri-bika21-miaww (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The putri-bika21-miaww package is part of a series of npm packages that have been linked to a token reward campaign by tea.xyz. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. The malicious nature of this package stems from its ability to modify critical files and republish variants, leading to potential pollution of the npm registry.

Vulnerability Detail

The vulnerability in the putri-bika21-miaww package originates from its inclusion in a malicious campaign that utilizes autopublish scripts to manipulate package.json files. This manipulation involves removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of unwanted packages in the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall putri-bika21-miaww

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-bika21-miaww package and any other related packages that may have been published as part of this malicious campaign. Regularly audit your package dependencies to ensure no malicious packages are included.

Conclusion

The putri-bika21-miaww package poses a significant risk due to its malicious code designed to manipulate package files and republish variants. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for putri-bika21-miaww →

Share this vulnerability

FAQ

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

If included in your project, this package can modify your package.json file and republish variants, potentially leading to security risks and pollution of the npm registry.

You should uninstall the putri-bika21-miaww package immediately and audit your dependencies for any other malicious packages.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall putri-bika21-miaww

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