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

putri-jamblang48-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107485: Malicious code in putri-jamblang48-ruro (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-jamblang48-ruro' 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 with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in 'putri-jamblang48-ruro' originates from malicious code embedded in the package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential exploitation of developers' reputations. The malicious payload is designed to operate silently, making it difficult for developers to detect its presence.

How To Fix

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

npm uninstall putri-jamblang48-ruro

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-jamblang48-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'putri-jamblang48-ruro' package poses a significant threat due to its embedded malicious code, which alters package metadata and can harm developer reputations. It is crucial to remove this package and monitor your projects for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for putri-jamblang48-ruro →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package metadata and repackages it under random names, leading to npm registry pollution.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Using this package can lead to reputation damage for developers and pollution of the npm registry, making it harder to find legitimate packages.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

If immediate removal is not possible, ensure to monitor your project closely for any unusual behavior and consider isolating the affected package.

How To Fix

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

npm uninstall putri-jamblang48-ruro

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