Malicious Code Injection in dewanto-brongkos33-ruro Package

dewanto-brongkos33-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101413: Malicious code in dewanto-brongkos33-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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The dewanto-brongkos33-ruro package is part of the npm ecosystem and appears to be involved in a token reward campaign associated with tea.xyz. This package is designed to generate and publish derivative packages with randomized names, 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 applications that depend on it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the dewanto-brongkos33-ruro package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants to pollute the npm registry, which can lead to security risks for developers and users relying on this package. The malicious behavior is part of a broader scheme to exploit npm's publishing system for fraudulent purposes.

How To Fix

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

npm uninstall dewanto-brongkos33-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 dewanto-brongkos33-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file does not include any references to this malicious package.

Conclusion

The dewanto-brongkos33-ruro package has been identified as containing malicious code that poses a significant risk to applications using it. It is essential to uninstall this package and monitor for any updates or patches that may address the vulnerability. Utilizing tools like Vulert can help keep your application secure by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for dewanto-brongkos33-ruro →

Share this vulnerability

FAQ

It is an npm package involved in a token reward campaign that has been identified as containing malicious code.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your application's security.

You should uninstall the dewanto-brongkos33-ruro package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

Currently, the best course of action is to uninstall the affected package. If a patched version is released, you will be able to update to it.

How To Fix

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

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