# PYSEC-2025-7: Posts scraped data to IP address associated with other malware distribution attacks.

> The imblog Python library exfiltrates scraped data to malicious IP addresses, posing a supply chain risk to users installing this 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:** 26 Feb 2025

## What is PYSEC-2025-7?

PYSEC-2025-7 is a vulnerability in imblog, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Published in 2021, the imblog package is a Python library
that scrapes data from a blog page to an IP address associated with other malware distribution attacks.

## Which versions are affected by PYSEC-2025-7?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `imblog` | PyPI | All versions | None |

## How do I fix PYSEC-2025-7?

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

## Is PYSEC-2025-7 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for PYSEC-2025-7 and fix it if it is affected.

What it is: PYSEC-2025-7 is a vulnerability in imblog, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of PYSEC-2025-7 in the wild and no public exploit code.

Affected packages and fixed versions:
- imblog (PyPI): affected all versions; 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-2025-7/ (Markdown: https://insights.sbomify.com/PYSEC-2025-7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/PYSEC-2025-7

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