# PYSEC-2022-250: The exotel project on PyPI was taken over via user account compromise via a phishing attack and a new malicious release made which contained

> Attackers can execute arbitrary code by installing a compromised Python package, affecting developers using the exotel library.

- **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:** No
- **Published:** 26 Aug 2022

## What is PYSEC-2022-250?

PYSEC-2022-250 is a vulnerability in exotel, published on 26 Aug 2022. 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

The exotel project on PyPI was taken over via user account compromise via a phishing attack and a new malicious release made which contained code which some environment variables and downloaded and ran malware at install time

## Which versions are affected by PYSEC-2022-250?

1 open source package ship an affected version, including exotel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `exotel` | PyPI | From 0.1.6 | None |

## How do I fix PYSEC-2022-250?

No fix has been published for PYSEC-2022-250 yet. Limit exposure of the affected software until one is available.

## Is PYSEC-2022-250 being exploited?

There is no known exploitation of PYSEC-2022-250 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for PYSEC-2022-250 and fix it if it is affected.

What it is: PYSEC-2022-250 is a vulnerability in exotel, published on 26 Aug 2022. 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 PYSEC-2022-250 in the wild and no public exploit code.

Affected packages and fixed versions:
- exotel (PyPI): affected from 0.1.6; 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/PYSEC-2022-250/ (Markdown: https://insights.sbomify.com/PYSEC-2022-250/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/PYSEC-2022-250

---
From sbomify Insights: https://insights.sbomify.com/PYSEC-2022-250/
Summaries are generated and may contain mistakes; the official description above is the record.