@zaip-ai/cli@7.1.0
OpenSSF/OSV Malicious Advisory
imported 7d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18364 confirms this npm version as malicious.
Independent LPM AI assessment
Manual ReviewIndependent AI assessment: manual_review. LPM AI review remains unresolved.
The launcher is shipped for explicit user activation, but its executable behavior could not be inspected because the offline analyzer does not support its format. Since that leaves material behavior unresolved, manual review is appropriate without claiming a confirmed attack.
Independent scan evidence
public snapshot- The manifest lists build, clean, typecheck, template sync, and prepack scripts; `init` is an explicit CLI command, with no install lifecycle hook shown.
- The template manifest includes the Windows launcher as a binary, and its README says to open it on Windows; the offline analysis could not inspect its executable behavior.
- The offline analysis reports a 12,800-byte artifact and an unsupported executable format, leaving the launcher’s behavior unresolved.
- The agent-related source matches were inspected: they concern Codex setup or activation and test or fixture code; the setup template checks for a host session transcript.
- The doctor source was inspected alongside its scanner finding; no source-established attack behavior was confirmed.
- The package source does not establish malicious behavior by the launcher.
- The README describes the launcher as user-opened and starting a hidden runtime, but that description does not resolve the executable’s behavior.
Source & flagged code
9 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/services/stack-git.jsView on unpkg · L1Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
Findings
Affected versions and remediation
This report applies to @zaip-ai/cli@7.1.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Avoid installing @zaip-ai/cli@7.1.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.