# MAL-2026-18124: Malicious code in journey-test-helloshell (PyPI)


- **Type:** Malicious package
- **Package:** `journey-test-helloshell` (PyPI)
- **Published:** 21 Oct 2026

## What is MAL-2026-18124?

MAL-2026-18124 is a malicious package in journey-test-helloshell, published on 21 Oct 2026. 

### Official description

setup.py registers a custom install command (cmdclass install hook) and also fires at module import that connects to the hardcoded bare-IP endpoint 137.131.233.62:8080 and bridges a /bin/bash -i subprocess over the socket, giving the operator interactive shell access on the installer's host. Before opening the shell, the code POSTs host identifiers (hostname, uid, JCX_ENVIRONMENT) over plaintext HTTP to http://137.131.233.62:443/shell-beacon. The install hook double-forks, calls setsid, redirects stdio to /dev/null, and enters an infinite reconnect loop with a 60-second sleep, persisting the backdoor beyond the pip install process. A /tmp/.jcx_channel.done guard file is used to coordinate the channel. Destination is a bare IP unrelated to any publisher domain.

In specific environments, package starts a reverse shell during installation.

---

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

Campaign: 2026-10-journey-test-helloshell

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.

 - The package overrides the install command in setup.py to execute malicious code during installation.

 - targetted-attack

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

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

## Sources

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

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