Malicious Code Injection in puteri-minta-mutiara Package: npm Vulnerability Overview

puteri-minta-mutiara Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164561: Malicious code in puteri-minta-mutiara (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The puteri-minta-mutiara package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This campaign aims to inflate developer reputation scores through the automatic generation and publication of packages with randomized names, which can lead to significant security risks.

Vulnerability Detail

The vulnerability in the puteri-minta-mutiara package stems from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can pollute the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include potential exposure to malicious code and the compromise of project integrity.

How To Fix

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

npm uninstall puteri-minta-mutiara

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 puteri-minta-mutiara package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The puteri-minta-mutiara package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages from their projects. Regular monitoring and updates can help mitigate such vulnerabilities.

See every vulnerability recorded for puteri-minta-mutiara →

Share this vulnerability

FAQ

The puteri-minta-mutiara package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the puteri-minta-mutiara package immediately using the command npm uninstall puteri-minta-mutiara.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall puteri-minta-mutiara

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