Malicious Code Injection in dewanto-rendang35-pore Package

dewanto-rendang35-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97689: Malicious code in dewanto-rendang35-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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The dewanto-rendang35-pore package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's ecosystem by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making the package a target for malicious activities.

Vulnerability Detail

The vulnerability in the dewanto-rendang35-pore package stems from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The malicious payload can significantly pollute the npm registry, affecting developers who rely on the integrity of the ecosystem. The origin of this vulnerability is linked to the broader issue of automated scripts that exploit npm for reputation manipulation.

How To Fix

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

npm uninstall dewanto-rendang35-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 dewanto-rendang35-pore package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to alert you in real-time for open-source 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 dewanto-rendang35-pore package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.

See every vulnerability recorded for dewanto-rendang35-pore →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores within the npm ecosystem.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should uninstall the dewanto-rendang35-pore package immediately and check for any other affected packages in your project.

Regularly update your packages, monitor your dependencies, and use tools like Vulert to stay informed about vulnerabilities.

There is no patch for the dewanto-rendang35-pore package itself; the best course of action is to uninstall it and avoid using similar packages.

How To Fix

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

npm uninstall dewanto-rendang35-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