# GHSA-x48m-gp6r-gp4v: Malicious Package in rate-map

> Attackers can execute malicious code and modify dependencies via a compromised npm package, requiring developers to upgrade immediately.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-x48m-gp6r-gp4v?

GHSA-x48m-gp6r-gp4v is a vulnerability in rate-map, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-x48m-gp6r-gp4v?

2 open source packages ship an affected version, including rate-map.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rate-map` | npm | From 1.0.3 | 1.0.5 |
| `rate-map` | npm | From 1.0.3 | 1.0.5 |

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

Upgrade rate-map to 1.0.5 or later.

## Is GHSA-x48m-gp6r-gp4v being exploited?

There is no known exploitation of GHSA-x48m-gp6r-gp4v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x48m-gp6r-gp4v and fix it if it is affected.

What it is: GHSA-x48m-gp6r-gp4v is a vulnerability in rate-map, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-x48m-gp6r-gp4v in the wild and no public exploit code.

Affected packages and fixed versions:
- rate-map (npm): affected from 1.0.3; fixed in 1.0.5
- rate-map (npm): affected from 1.0.3; fixed in 1.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-x48m-gp6r-gp4v/ (Markdown: https://insights.sbomify.com/GHSA-x48m-gp6r-gp4v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x48m-gp6r-gp4v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x48m-gp6r-gp4v/
Summaries are generated and may contain mistakes; the official description above is the record.