Malicious code in @zaip-ai/cli (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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

Source: amazon-inspector (0e44ea3cafd9835a85d3305b6aa9ed2f5400546938c6430c19a30cbdc5398936) @zaip-ai/cli@7.2.0 is a CLI package whose shipped files trigger keyword co-occurrence patterns (curl/wget/ping tokens, Buffer.from base64 decoding) without evidence of installer-side harm. The curl references in dist/services/codex-pre-tool-hook-template.test.js and dist/services/codex-pre-tool-policy-template.js appear inside test fixtures and policy templates that enumerate example command strings (including explicit placeholder hosts such as evil.test and example.com) used by a pre-tool hook/policy mechanism — the strings are policy data, not executed commands against those hosts. Buffer.from(..., 'base64').toString(...) usage in dist/services/global-codex-config.js and in a release-preparation script is ordinary base64 decoding of configuration/release data, with no eval, Function constructor, or dynamic code execution of the…

Published by the source

28 Oct 2026, 20:37 UTC

Last modified by the source

29 Oct 2026, 14:30 UTC

Source last checked

30 Oct 2026, 06:15 UTC

1. Revision 2 · amended · 30 Oct 2026

   Amended from osv record MAL-2026-18364

2. Revision 1 · created · 29 Oct 2026

   Published from osv record MAL-2026-18364

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

# Patch Next advisory brief: GHSA-ffq4-h5jm-8pqr

Advisory: Malicious code in @zaip-ai/cli (npm)
IDs: GHSA-ffq4-h5jm-8pqr
Record: https://patchnext.com/advisories/mal-2026-18364 (revision 2, source checked 30 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
- npm @zaip-ai/cli: affected >= 7.3.0, <= 7.3.0; >= 7.0.0, <= 7.0.0; >= 7.1.0, <= 7.1.0; >= 7.4.0, <= 7.4.0; >= 6.5.0, <= 6.5.0; >= 7.2.0, <= 7.2.0; >= 6.4.0, <= 6.4.0

## Suggested inspection (read-only)
- `npm ls @zaip-ai/cli --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 @zaip-ai/cli.
- 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-18364 (OSV record MAL-2026-18364 lists affected ranges: npm @zaip-ai/cli >=7.3.0 =7.0.0 =7.1.0 =7.4.0 =6.5.0 =7.2.0 =6.4.0 <=6.4.0)

Commands are suggestions: review each one before running it.