# MAL-2026-18045: Malicious code in asurion (PyPI)


- **Type:** Malicious package
- **Package:** `asurion` (PyPI)
- **Published:** 19 Oct 2026

## What is MAL-2026-18045?

MAL-2026-18045 is a malicious package in asurion, published on 19 Oct 2026. 

### Official description

setup.py executes at `pip install` time and POSTs a JSON payload containing the full `os.environ` dictionary along with hostname, username, current working directory, and platform details to the hardcoded endpoint https://webhook.site/b2967b0a-1b24-4670-8ae1-e09e3cf272c4 via urllib.request. Environment variables on developer and CI hosts routinely contain credential-grade secrets (AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, database passwords, cloud session tokens), so this install-time beacon is a bulk credential-sweep. The package name, implausibly high version number, and single webhook.site exfil destination are consistent with a dependency-confusion canary/exfil payload targeting an internal `asurion` namespace.

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

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

## Sources

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

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