Malicious Code Injection in candra-sego86-ruro Package: A Threat to npm Users

candra-sego86-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100242: Malicious code in candra-sego86-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 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 candra-sego86-ruro package is part of the npm ecosystem, primarily 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 malicious due to its capability to modify package.json files and republish variants with altered names and versions.

Vulnerability Detail

The vulnerability stems from the package's malicious payload that alters the package.json file by removing private flags and changing version numbers. It generates random names for packages, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may inadvertently use these malicious packages, exposing their applications to further risks.

How To Fix

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

npm uninstall candra-sego86-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, avoid using the candra-sego86-ruro package and monitor your project for any dependencies that may have inadvertently included it. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The candra-sego86-ruro package poses a significant risk to npm users due to its malicious code that alters package configurations and repopulates the npm registry with harmful variants. It is crucial to remove this package and utilize monitoring tools like Vulert to safeguard your applications against similar threats.

See every vulnerability recorded for candra-sego86-ruro →

Share this vulnerability

FAQ

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

The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security.

You should uninstall the package immediately using npm uninstall candra-sego86-ruro and check for any other affected dependencies.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities using just your package-lock.json.

How To Fix

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

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