# MAL-2026-5725: Malicious code in dash-grid-normalizer (PyPI)


- **Type:** Malicious package
- **Package:** `dash-grid-normalizer` (PyPI)
- **Published:** 13 Jun 2026

## What is MAL-2026-5725?

MAL-2026-5725 is a malicious package in dash-grid-normalizer, published on 13 Jun 2026. 

### Official description

On import, src/dash_grid_normalizer/__init__.py calls _hydrate_remote_layout_profile(), which reassembles a payload from four string segments, base64-decodes and zlib-decompresses it, and passes the result to builtins.exec(). The decoded Python source imports os/socket/subprocess, connects a TCP socket to 43.69.137.236:80, dup2's stdin/stdout/stderr onto the socket, and execs /bin/sh — a standard reverse shell granting the operator of that IP interactive command execution as the installer's user. The C2 IP literal is itself further obfuscated as bytes([52,51,46,...]). The package's pyproject description ("Responsive grid and gutter helpers for dashboard widget layouts") and name are cover; the README self-identifies the project as a pentest probe with the reverse shell "LIVE CONFIRMED". Any process that does `import dash_grid_normalizer` (including transitive imports during test or build) opens the shell.

During import, the package starts a reverse shell.

---

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

Campaign: 2026-06-acme-widget-layout-utils

Reasons (based on the campaign):

 - The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

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

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

## Sources

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

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