Malicious Code Injection in putri-poke5: A Threat to npm Packages

putri-poke5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164587: Malicious code in putri-poke5 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'putri-poke5' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in 'putri-poke5' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The malicious payload is executed through scripts such as auto.js and autopublish.js, which are included in the package.

How To Fix

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

npm uninstall putri-poke5

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 'putri-poke5' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'putri-poke5' package poses a significant 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 regularly audit their dependencies to maintain the integrity of their applications.

See every vulnerability recorded for putri-poke5 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

You should uninstall the package immediately using 'npm uninstall putri-poke5' and audit your project for other potentially vulnerable packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.

Using compromised packages can lead to security breaches, data leaks, and the pollution of the npm registry, which can affect other developers and projects.

How To Fix

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

npm uninstall putri-poke5

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