registry / @zaip-ai/cli / 5.7.0
@zaip-ai/cli@5.7.0
⚠ Under reviewCLI oficial para instalar e configurar o ZAIP-AIOS em qualquer repositório
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest has no npm install lifecycle hook, and inspected source does not substantiate the scanner's claim that doctor activates the hidden executable. Because a required binary artifact cannot be assessed through source citations and the agent integration is not fully resolved, manual review is warranted.
Static reason
One or more suspicious static signals were detected.
Trigger
Unresolved; the executable artifact's behavior could not be inspected as UTF-8 source.
Impact
Unknown; source inspection cannot establish the binary artifact's effect.
Mechanism
The available source shows project-file checks and agent-hook references, but does not establish malicious execution or a complete activation path for the binary.
AI rationale
The manifest has no npm install lifecycle hook, and inspected source does not substantiate the scanner's claim that doctor activates the hidden executable. Because a required binary artifact cannot be assessed through source citations and the agent integration is not fully resolved, manual review is warranted.
Decision evidence
public snapshotAI called this Manual Review at 84.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json exposes a CLI and has no preinstall, install, or postinstall hook.
- The inspected doctor code checks project files and reports missing files; it does not establish that it loads the flagged executable.
- The Codex hook files and related configuration references establish an agent integration surface, but the inspected evidence does not resolve all of its behavior.
- The required design executable is binary and cannot be assessed through source citations, so clean status is not established.
Evidence against
- The manifest lists only build, clean, typecheck, template sync, and prepack scripts; no npm install lifecycle hook is present.
- The stack-git excerpt invokes system Git on non-Windows platforms as part of a named setup function.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/services/stack-git.jsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
...
L5: import { promisify } from "node:util";
L6: import { inflateRawSync } from "node:zlib";
L7: import { assertSafeDestination } from "./transactional-files.js";
L8: const exec = promisify(execFile);
L9: const API = "https://api.github.com/repos/git-for-windows/git/releases/latest";
L10: const KNOWN_DIGESTS = {
...
L12: };
L13: export function resolveGitForWindowsRelease(value, arch = process.arch) {
L14: const release = value;
...
L34: try {
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/services/stack-git.jsView on unpkg · L1templates/.agents/design/zaip-design.exeView file
•path = templates/.agents/design/zaip-design.exe
kind = payload_in_excluded_dir
sizeBytes = 7680
magicHex = [redacted]
High
Payload In Excluded Dir
Package hides binary, compressed, or executable-looking payloads in test/fixture/hidden paths.
templates/.agents/design/zaip-design.exeView on unpkgFindings
1 Critical3 High7 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/services/doctor.js
HighSandbox Evasion Gated Capabilitydist/services/stack-git.js
HighPayload In Excluded Dirtemplates/.agents/design/zaip-design.exe
HighSemantic Analysis Limiteddist/services/codex-pre-tool-hook-template.test.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarytemplates/.agents/design/zaip-design.exe
MediumShips Build Helpertemplates/.agents/design/packages/windows-launcher/build-design-launcher.ps1
MediumOversized Source Filetemplates/.agents/runtime/bin/zaip.mjs
MediumOversized Cli Entrypointtemplates/.agents/runtime/bin/zaip.mjs
Affected versions and remediation
This report applies to @zaip-ai/cli@5.7.0.
See all versions of @zaip-ai/cli for other recorded verdicts.
- Review the evidence and your use of @zaip-ai/cli@5.7.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.