# GHSA-486g-47cc-8wxf: aiocpa contains credential harvesting code

> Malicious code in aiocpa library steals Crypto Pay credentials and sends them to a remote bot, requiring immediate removal of the package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2024

## What is GHSA-486g-47cc-8wxf?

GHSA-486g-47cc-8wxf is a vulnerability in aiocpa, published on 25 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

aiocpa is a user-facing library for generating color gradients of text. Version 0.1.13 introduced obfuscated, malicious code targeting Crypto Pay users, forwarding client credentials to a remote Telegram bot. All versions have been removed from PyPI.

## Which versions are affected by GHSA-486g-47cc-8wxf?

2 open source packages ship an affected version, including aiocpa.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aiocpa` | PyPI | From 0.1.13 to 0.1.14 | None |
| `aiocpa` | PyPI | From 0.1.13 to 0.1.14 | None |

## How do I fix GHSA-486g-47cc-8wxf?

No fix has been published for GHSA-486g-47cc-8wxf yet. Limit exposure of the affected software until one is available.

## Is GHSA-486g-47cc-8wxf being exploited?

There is no known exploitation of GHSA-486g-47cc-8wxf in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-486g-47cc-8wxf and fix it if it is affected.

What it is: GHSA-486g-47cc-8wxf is a vulnerability in aiocpa, published on 25 Nov 2024. 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-486g-47cc-8wxf in the wild and no public exploit code.

Affected packages and fixed versions:
- aiocpa (PyPI): affected from 0.1.13 up to 0.1.14; no fix listed
- aiocpa (PyPI): affected from 0.1.13 up to 0.1.14; no fix listed

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-486g-47cc-8wxf/ (Markdown: https://insights.sbomify.com/GHSA-486g-47cc-8wxf/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-486g-47cc-8wxf

---
From sbomify Insights: https://insights.sbomify.com/GHSA-486g-47cc-8wxf/
Summaries are generated and may contain mistakes; the official description above is the record.