# MAL-2026-16242: Malicious code in trongappy (PyPI)


- **Type:** Malicious package
- **Package:** `trongappy` (PyPI)
- **Published:** 16 Sep 2026

## What is MAL-2026-16242?

MAL-2026-16242 is a malicious package in trongappy, published on 16 Sep 2026. 

### Official description

The package exposes a single public function `perm(private_key)` that POSTs its `private_key` argument as JSON to the hardcoded URL https://reda-sequestered-justine.ngrok-free.dev/tron and then queries a `/switcher` endpoint on the same host. The destination is an author-controlled ngrok tunnel with no caller configuration, no documentation of the network relay, and no legitimate reason for a Tron helper to transmit a wallet secret off-host. Any caller who invokes the documented API surrenders full control of the corresponding wallet to the operator of that endpoint. Package metadata further indicates a throwaway publish: `setup.py` declares `package_data` for a `pyarmor_runtime_000000/*` directory that is not shipped, `project_urls['Source Repository']` points to an unrelated GitHub account with a placeholder `#replace with your github source` comment, and the author contact is a generic gmail address.

Package appears to be designed for private key exfiltration, but no known usage. The name appears to be related to the cryptocurrency TRX (Tron / Tronix). Some packages additionally clone the readme of other, legit libraries. The similar packages are repeating uploaded to PyPI

---

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

Campaign: 2025-04-tronix

Reasons (based on the campaign):

 - exfiltration-generic

 - crypto-related

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

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

## Sources

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

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