Malicious Code Detected in candra-telur17-ruro Package - npm Vulnerability

candra-telur17-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100250: Malicious code in candra-telur17-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-telur17-ruro package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that manipulate developer reputation scores. This package, like others in the campaign, is designed to generate and publish derivative packages automatically, which can lead to significant issues in the npm ecosystem.

Vulnerability Detail

The vulnerability in the candra-telur17-ruro package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. This behavior is intended to inflate developer reputation scores fraudulently and pollute the npm registry with numerous variants of the package. The ramifications include potential security risks for applications relying on this package, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall candra-telur17-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-telur17-ruro package altogether. If it is already included in your project, ensure that you monitor your dependencies closely and consider using tools like Vulert to check for vulnerabilities. You can use the following command to check your package-lock.json for vulnerabilities: vulert check package-lock.json.

Conclusion

The candra-telur17-ruro package contains malicious code that poses a significant risk to applications using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for candra-telur17-ruro →

Share this vulnerability

FAQ

The candra-telur17-ruro package is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the candra-telur17-ruro package immediately and monitor your dependencies for any other malicious packages.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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