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

putri-tiwul41-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89797: Malicious code in putri-tiwul41-riris (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 package 'putri-tiwul41-riris' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious design of the package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers. The malicious payload can compromise the security of applications relying on this package, leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall putri-tiwul41-riris

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 prevent the installation of this package by using the following command to uninstall it: npm uninstall putri-tiwul41-riris. Additionally, consider using package-lock.json to monitor dependencies and ensure no malicious packages are included.

Conclusion

The 'putri-tiwul41-riris' package poses a significant security risk due to its malicious code designed to manipulate npm packages. It is crucial for developers to be vigilant about their dependencies and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove the affected package and ensure the security of your applications.

See every vulnerability recorded for putri-tiwul41-riris →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized modifications of your project's dependencies, potentially compromising application security.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the package using 'npm uninstall putri-tiwul41-riris' and check for any other dependencies that may be affected.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

Signs include unexpected behavior, unauthorized access, or changes in your application's performance. Always review your dependencies for any suspicious activity.

How To Fix

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

npm uninstall putri-tiwul41-riris

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