Malicious Code Injection in candra-rangi56-pore Package

candra-rangi56-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97637: Malicious code in candra-rangi56-pore (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-rangi56-pore package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This package, like others in its category, has been identified as containing malicious scripts that compromise its integrity.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the candra-rangi56-pore package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior pollutes the npm registry and can severely impact developers by inflating reputation scores fraudulently and potentially introducing security risks into their projects.

How To Fix

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

npm uninstall candra-rangi56-pore

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 candra-rangi56-pore package and replace it with a trusted alternative that provides similar functionality without the associated risks. Always review the packages you intend to use for any known vulnerabilities.

Conclusion

The candra-rangi56-pore package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for candra-rangi56-pore →

Share this vulnerability

FAQ

The candra-rangi56-pore package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to reputation inflation and potential security risks.

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

You should uninstall the candra-rangi56-pore package immediately using the command npm uninstall candra-rangi56-pore and replace it with a secure alternative.

Yes, you should look for reputable packages that provide similar functionality but do not have a history of malicious behavior. Always review the package's reputation and security history.

How To Fix

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

npm uninstall candra-rangi56-pore

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