# MAL-2026-5518: Malicious code in hello-dynamic (PyPI)


- **Type:** Malicious package
- **Package:** `hello-dynamic` (PyPI)
- **Published:** 10 Jun 2026

## What is MAL-2026-5518?

MAL-2026-5518 is a malicious package in hello-dynamic, published on 10 Jun 2026. 

### Official description

hello-dynamic 0.1.2 is a near-empty package whose __init__.py only defines a hello() function printing 'Hello!'. Its setup.cfg declares a dependency_links entry pointing at a webhook.site UUID endpoint (https://webhook.site/56557fe9-5bcf-4f26-bed7-38f772525011/pypi/aliga-raison). webhook.site is a generic HTTP-callback inspector commonly used to receive beacon traffic. Modern pip ignores dependency_links, so installer harm is minimal in practice, but the artifact's shape — trivial code, no real functionality, install metadata pointing at a request-inspector endpoint named after a PyPI package — is consistent with a reconnaissance probe testing which installers still process dependency_links. No exfiltration, RCE, credential read, or persistence mechanism is present in the package code.

Package attempts to test exploitation via legacy dependency_links configuration

---

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

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

## Sources

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

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