Malicious Code Injection in candra-dradag28-ruro Package

candra-dradag28-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100218: Malicious code in candra-dradag28-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 candra-dradag28-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that alters its own package.json file and publishes variants to the npm registry.

Vulnerability Detail

The vulnerability in the candra-dradag28-ruro package stems from its malicious payload, which modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of developer environments. The origin of this vulnerability is linked to the tea.xyz token reward campaign that has been flooding the npm ecosystem with malicious packages.

How To Fix

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

npm uninstall candra-dradag28-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 prevent the installation of this malicious package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include candra-dradag28-ruro in its dependencies.

Conclusion

The candra-dradag28-ruro package poses a significant security risk due to its malicious code that alters package metadata and publishes variants to the npm registry. It is crucial to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for candra-dradag28-ruro →

Share this vulnerability

FAQ

candra-dradag28-ruro is an npm package associated with the tea.xyz token reward campaign, designed to publish derivative packages automatically.

The vulnerability can lead to unauthorized modifications in your project, potentially compromising sensitive data and polluting the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should remove the candra-dradag28-ruro package from your project immediately and monitor for any updates or patches.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities using just the package-lock.json file.

How To Fix

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

npm uninstall candra-dradag28-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