Malicious code in @zaip-ai/cli (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npm@zaip-ai/cli
“@zaip-ai/cli” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (7)
- 6.4.0
- 6.5.0
- 7.0.0
- 7.1.0
- 7.2.0
- 7.3.0
- 7.4.0
purl: pkg:npm/%40zaip-ai/cli
Sources (8)
ghsa-malware
GHSA-ffq4-h5jm-8pqrVersions from this source: 7.3.0, 7.0.0, 7.1.0, 7.4.0, 6.5.0, 7.2.0, 6.4.0
sha256: 6871bd0117df69d113dc6e42ef94d417f866e24b30e2b2b0484a2cb934473443
amazon-inspector
IN-MAL-2026-022117Versions from this source: 6.4.0
sha256: 2712209fc8f6891e225ed01848b4321decb7f98d2d8bc79d0f6b10dc9766b1d7
amazon-inspector
IN-MAL-2026-022110Versions from this source: 7.0.0
sha256: 45f0458bd561ea88b54454f9ac2ff941f3e98ffb3ad715498aa75a0fb01e5534
amazon-inspector
IN-MAL-2026-022111Versions from this source: 6.5.0
sha256: 861d3d7318c6bfadb53b44631e8cd6f7d0d934c5fb74928a0a37b1285889303f
amazon-inspector
IN-MAL-2026-022106Versions from this source: 7.4.0
sha256: 9fb7dac2e2cca3fc9e84a9bda29e04ab16211e5d8be08c8a497ed1f44db0ad81
amazon-inspector
IN-MAL-2026-022104Versions from this source: 7.1.0
sha256: dbf61a4e849158426533ddce967b531d2d266d337a1a8ef7d4985ad14d68487e
amazon-inspector
IN-MAL-2026-022105Versions from this source: 7.3.0
sha256: e24938121e390afa724553ee07a42e21d35a7b50b2ae87aea5840cf10a98217c
amazon-inspector
IN-MAL-2026-022155Versions from this source: 7.2.0
sha256: 0e44ea3cafd9835a85d3305b6aa9ed2f5400546938c6430c19a30cbdc5398936
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= 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 decoded bytes. The ping/POST/GET tokens in templates/.agents/tools/runtime/api-mcp-runtime.mjs come from an MCP runtime template describing HTTP method handling. No lifecycle scripts fetch remote code, no installer secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser stores) are read, no hardcoded attacker C2 endpoint is bound to a network call, and no obfuscated destination is present.
Source: ghsa-malware (6871bd0117df69d113dc6e42ef94d417f866e24b30e2b2b0484a2cb934473443)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.