Malicious Code Injection in candra-lutis64-ruro Package

candra-lutis64-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100226: Malicious code in candra-lutis64-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 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 candra-lutis64-ruro package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the candra-lutis64-ruro package involves malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and republishing of derivative packages. The malicious payload can lead to significant pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.

How To Fix

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

npm uninstall candra-lutis64-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 workaround, you can avoid using the candra-lutis64-ruro package altogether. If it is already included in your project, consider removing it and replacing it with a trusted alternative. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities and receive real-time alerts.

Conclusion

The candra-lutis64-ruro package contains malicious code that poses a significant risk to developers and the integrity of the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities. Staying vigilant and informed will help protect your applications from similar threats.

See every vulnerability recorded for candra-lutis64-ruro →

Share this vulnerability

FAQ

The candra-lutis64-ruro package is an npm package associated with a token reward campaign that generates and publishes derivative packages.

The malicious code can modify your package.json file, remove private flags, and republish variants, leading to potential security risks and pollution of the npm registry.

You should remove the candra-lutis64-ruro package from your project and monitor for any updates or patches that may be released.

Yes, Vulert allows you to monitor your package-lock.json for vulnerabilities without requiring code access or installation. You can use the Vulert playground to check if your application is affected.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.

How To Fix

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

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