Which versions of rc are affected by GHSA-G2Q5-5433-RHRF?

rc (npm) versions = 1.2.9 is affected.

Is there a fix for GHSA-G2Q5-5433-RHRF?

No fixed version is listed for GHSA-G2Q5-5433-RHRF yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-G2Q5-5433-RHRF exploitable, and should I be worried?

Whether GHSA-G2Q5-5433-RHRF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-G2Q5-5433-RHRF is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-G2Q5-5433-RHRF in rc

GHSA-G2Q5-5433-RHRF

GHSA-G2Q5-5433-RHRF is a critical-severity security vulnerability in rc (npm), affecting versions = 1.2.9. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Embedded malware in rc

The npm package rc had versions published with malicious code. Users of affected versions (1.2.9, 1.3.9, and 2.3.9) should downgrade to 1.2.8 as soon as possible and check their systems for suspicious activity.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Impact

Affected versions

rc (= 1.2.9) rc (= 1.3.9) rc (= 2.3.9)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for GHSA-G2Q5-5433-RHRF yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-G2Q5-5433-RHRF? GHSA-G2Q5-5433-RHRF is a critical-severity security vulnerability in rc (npm), affecting versions = 1.2.9. No fixed version is listed yet.
Which versions of rc are affected by GHSA-G2Q5-5433-RHRF? rc (npm) versions = 1.2.9 is affected.
Is there a fix for GHSA-G2Q5-5433-RHRF? No fixed version is listed for GHSA-G2Q5-5433-RHRF yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-G2Q5-5433-RHRF exploitable, and should I be worried? Whether GHSA-G2Q5-5433-RHRF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-G2Q5-5433-RHRF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.