# MAL-2026-13729: Malicious code in dlmm-sdk (PyPI)


- **Type:** Malicious package
- **Package:** `dlmm-sdk` (PyPI)
- **Published:** 11 Aug 2026

## What is MAL-2026-13729?

MAL-2026-13729 is a malicious package in dlmm-sdk, published on 11 Aug 2026. 

### Official description

The package's top-level module runs a report() routine on import, and setup.py invokes the same import at install time. The routine collects environment variables matching secret-shaped keywords (KEY, TOKEN, SECRET, AWS, GITHUB, NPM, MNEMONIC, WALLET, SOLANA, HELIUS,...), reads ~/.npmrc and ~/.gitconfig, enumerates ~/.ssh, ~/.aws, ~/.config/solana, ~/.config/anchor, and ~/.config/gcloud, and gathers hostname, username, cwd, and platform. The collected JSON is POSTed via urllib.request.urlopen to a hardcoded webhook.site endpoint (https://webhook.site/326b0891-2093-4800-a4c1-686ce3e07b09). Module docstring and setup.py comment label the behavior 'environment diagnostics,' but the code path is bulk credential and host-identity exfiltration to a non-first-party collector. The package name resembles Meteora's DLMM SDK.

During import the package exfiltrates sensitive env variables (e.g. related to cloud providers, cryptocurrencies, package registries), credential files (including SSH keys, cloud credentials, package registry configuration) and dotenv files. In addition, listings of some directories, e.g. cryptocurrency wallets and cloud CLI configuration, are collected.

---

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-08-dlmm

Reasons (based on the campaign):

 - exfiltration-env-variables

 - dependency-confusion

 - crypto-related

 - exfiltration-credentials

 - files-exfiltration

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

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

## Sources

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

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