Malicious Code Injection in putri-nasi4-tititugel Package

putri-nasi4-tititugel Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98273: Malicious code in putri-nasi4-tititugel (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The putri-nasi4-tititugel package is part of the npm ecosystem, often used in JavaScript projects. It appears to be associated with the tea.xyz token reward campaign, which has been linked to various malicious activities. This package is designed to manipulate npm registry entries and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the putri-nasi4-tititugel package stems from its inclusion in a series of malicious packages that modify the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, polluting the npm registry. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to unauthorized access or manipulation of their projects.

How To Fix

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

npm uninstall putri-nasi4-tititugel

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-nasi4-tititugel package and replace it with a trusted alternative. Additionally, ensure that your package-lock.json file is monitored for vulnerabilities using tools like Vulert, which can alert you in real-time about open-source vulnerabilities without requiring code access.

Conclusion

The putri-nasi4-tititugel package poses a significant security risk due to its malicious code that alters package metadata and republish behavior. It is crucial for developers to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for putri-nasi4-tititugel →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for malicious activities.

It can lead to unauthorized modifications in your package.json file and potentially compromise your project's security.

You should uninstall the package immediately and monitor your project for any further vulnerabilities.

Yes, you can use Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

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

How To Fix

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

npm uninstall putri-nasi4-tititugel

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