# MAL-2026-11426: Malicious code in trtllm-subdir-test (PyPI)


- **Type:** Malicious package
- **Package:** `trtllm-subdir-test` (PyPI)
- **Published:** 1 Aug 2026

## What is MAL-2026-11426?

MAL-2026-11426 is a malicious package in trtllm-subdir-test, published on 1 Aug 2026. 

### Official description

setup.py performs an unconditional HTTP GET to the hardcoded bare-IP URL http://167.233.212.138/cb/db27bcff144c059f/trtllm_subdir_test at install time (wrapped in try/except at module top-level, timeout=5). The path segment encodes the package name, giving the operator confirmation of a successful install and identification of the installer host by its source IP. The package version 99999.0.1 is a dependency-confusion sentinel version-number pattern designed to win resolution against a lower-versioned internal package of the same name; installing this artifact therefore signals to the operator that an organization's build system resolved a public typosquat/confusion package in place of a private one.

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

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

## Sources

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

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