How severe is GHSA-x48m-gp6r-gp4v?

GHSA-x48m-gp6r-gp4v has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x48m-gp6r-gp4v?

GHSA-x48m-gp6r-gp4v affects the following packages: rate-map (npm). Ecosystems affected: npm.

How do I fix GHSA-x48m-gp6r-gp4v?

Update rate-map to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x48m-gp6r-gp4v is resolved across your whole dependency graph.

How do I detect GHSA-x48m-gp6r-gp4v in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rate-map, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x48m-gp6r-gp4v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-x48m-gp6r-gp4v actively exploited in the wild?

No public exploit code has been indexed for GHSA-x48m-gp6r-gp4v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-x48m-gp6r-gp4v published, and has it been updated?

GHSA-x48m-gp6r-gp4v was published on September 3, 2020 and was last updated on September 30, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

CRITICAL severity

Malicious Package in rate-mapGHSA-x48m-gp6r-gp4v

CRITICAL

GHSA-x48m-gp6r-gp4v is a critical-severity (CVSS 9.8) vulnerability in rate-map. A fix is available for rate-map — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 30, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 30, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

rate-mapnpm

270downloads / week

Description

Version 1.0.3 of rate-map contains malicious code. The malware breaks functionality of the purescript-installer package by rewriting code of the dl-tar dependency.

Recommendation

Upgrade to version 1.0.5 or later. There is no indication of further compromise.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`rate-map`	≥ 1.0.3&&< 1.0.5	1.0.5`npm install rate-map@1.0.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rate-map, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rate-map to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x48m-gp6r-gp4v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Version 1.0.3 of `rate-map` contains malicious code. The malware breaks functionality of the `purescript-installer` package by rewriting code of the `dl-tar` dependency. ## Recommendation Upgrade to version 1.0.5 or later. There is no indication of further compromise.

O3 Security · Impact-Aware SCA

Is GHSA-x48m-gp6r-gp4v in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works