Malicious Code Injection in putri-keripik23-pore Package

putri-keripik23-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98265: Malicious code in putri-keripik23-pore (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-keripik23-pore package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the putri-keripik23-pore package stems from its malicious payload, which 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 that pollute the npm registry, potentially affecting other packages and developers relying on npm for legitimate packages. The origin of this issue is linked to a broader campaign that exploits npm's publishing mechanisms for malicious purposes.

How To Fix

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

npm uninstall putri-keripik23-pore

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-keripik23-pore package and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The putri-keripik23-pore package contains a serious vulnerability due to malicious code that compromises its functionality and the npm registry. It is crucial to uninstall this package and monitor your project for vulnerabilities to maintain security.

See every vulnerability recorded for putri-keripik23-pore →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that automates the generation and publication of derivative packages.

The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, affecting other packages.

You should uninstall the package immediately using 'npm uninstall putri-keripik23-pore' and check your project for any other vulnerabilities.

Yes, regularly update your dependencies, use trusted sources, and employ tools like Vulert to monitor for vulnerabilities in real-time.

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-keripik23-pore

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