# GHSA-4f84-67cv-qrv3: A single post-release of dydx-v4-client contained obfuscated multi-stage loader

> A compromised PyPI account uploaded a malicious version of dydx-v4-client containing an obfuscated loader that executes arbitrary code on the host.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Feb 2026

## What is GHSA-4f84-67cv-qrv3?

GHSA-4f84-67cv-qrv3 is a vulnerability in dydx-v4-client, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A PyPI user account compromised by an attacker and was able to upload a malicious version (1.1.5.post1) of the `dydx-v4-client` package. This version contains a highly obfuscated multi-stage loader that ultimately executes malicious code on the host system.

While the final payload is not visible because it is tucked away inside 100 layers of encoding, the structural design—specifically the use of recursive decompression followed by an `exec()` call is a definitive indicator of malicious software, likely a "Crypter" or "Dropper" masquerading as a cryptocurrency-related utility with the intent on connecting to hxxps://dydx[.]priceoracle[.]site/py
to download and execute further payloads.

Users of the `dydx-v4-client` package should immediately uninstall version 1.1.5.post1and revert to the last known good version (1.1.5) or later secure versions once available. Additionally, users should monitor their systems for any unusual activity and consider running security scans to detect any potential compromise.

## Which versions are affected by GHSA-4f84-67cv-qrv3?

2 open source packages ship an affected version, including dydx-v4-client.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dydx-v4-client` | PyPI | From 1.1.5.post1 | 1.1.5 |
| `dydx-v4-client` | PyPI | From 1.1.5.post1 | 1.1.5 |

## How do I fix GHSA-4f84-67cv-qrv3?

Upgrade dydx-v4-client to 1.1.5 or later.

## Is GHSA-4f84-67cv-qrv3 being exploited?

There is no known exploitation of GHSA-4f84-67cv-qrv3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4f84-67cv-qrv3 and fix it if it is affected.

What it is: GHSA-4f84-67cv-qrv3 is a vulnerability in dydx-v4-client, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-4f84-67cv-qrv3 in the wild and no public exploit code.

Affected packages and fixed versions:
- dydx-v4-client (PyPI): affected from 1.1.5.post1; fixed in 1.1.5
- dydx-v4-client (PyPI): affected from 1.1.5.post1; fixed in 1.1.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-4f84-67cv-qrv3/ (Markdown: https://insights.sbomify.com/GHSA-4f84-67cv-qrv3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4f84-67cv-qrv3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4f84-67cv-qrv3/
Summaries are generated and may contain mistakes; the official description above is the record.