@ikyyofc/gemini-cli
AI Agent CLI — native function calling · GEMINI.md context · extensions
This report shows the evidence for @ikyyofc/gemini-cli@5.0.5. 17 of 17 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4394 confirms this npm version as malicious.
Advisory
MAL-2026-4394
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @ikyyofc/gemini-cli (npm)
Details
@ikyyofc/gemini-cli@3.0.1 ships two heavily obfuscated modules (src/gemini.js and src/utils/proxy.js) wrapped in an obfuscator.io-style string-array + RC4-XOR decoder (220-entry encrypted string array, hex-mangled identifiers like `_0x4693ef`, `_0x29cf`). Decoding reveals two coordinated behaviors that make this package unsafe for installers to use:
1. Spoofed Google/Firebase Android-app identity for Gemini access. src/gemini.js exposes a getToken() that POSTs to a hidden URL with hardcoded `X-Android-Package`, `X-Android-Cert` (SHA1 cert fingerprint), and `X-Firebase-GMPID` headers plus a hardcoded `clientType`, then attaches the returned Bearer token to Gemini API calls. The CLI never asks the user for a Google API key; instead it ships a third-party Android application's identity to mint Gemini tokens on the installer's behalf. Every installer who uses the CLI is making Google Gemini API calls under a stolen client identity, exposing them to abuse-of-service and ToS-violation consequences if Google revokes or flags that identity.
2. Silent relay through a hardcoded pool of ~13 third-party proxies. index.js calls `setupGlobalProxy()` at startup, which installs a global axios request interceptor in src/utils/proxy.js that rewrites every outgoing request URL via `wrapUrl(proxy, originalUrl)` to traverse one of ~13 hardcoded proxy hosts. The user's chat prompts and attached file contents (up to 20 MB) are carried in the Gemini POST body and therefore visible in cleartext to the proxy operators. The README does not disclose any proxy/relay behavior; the proxy list is encrypted within the obfuscated bundle to prevent users discovering it through source review.
The combination — obfuscation that hides the data flow, spoofed third-party credentials carrying the installer's API requests, and an undisclosed third-party relay reading prompt content and the Bearer token — is a silent-relay supply-chain pattern. Any developer who installs and runs this CLI leaks the contents of their conversations and any file they attach to operators they never consented to trust, while also operating under a credential that does not belong to them.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @ikyyofc/gemini-cli@5.0.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @ikyyofc/gemini-cli@5.0.5. 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: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.