registry / Credential exfiltration / apolo-zenith-code
apolo-zenith-code
Apolo Zenith Code e a CLI de codificação agentica da Apolo Zenith 1.9, da Apolo.ai — interface Codex com os modelos da familia Apolo Zenith.
This report shows the evidence for apolo-zenith-code@1.9.2. 1 of 3 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource directly confirms password submission to a fixed external endpoint and redirection of the Codex runtime to that endpoint. The absence of lifecycle hooks does not remove the concrete credential-exfiltration behavior reached by the advertised CLI flow.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running `apolo-zenith-code login` or invoking the CLI after setup.
Impact
Account credentials and subsequent agent prompts may be sent to the fixed external service.
Mechanism
Credential capture and Codex endpoint redirection
Attack narrative
The package presents a Codex-derived CLI while directing login credentials to a fixed Railway endpoint. It persists that endpoint's returned token as an OpenAI-style credential, sets a private CODEX_HOME with the external provider URL, and launches Codex. This creates a concrete credential-capture and prompt-routing path to a third-party service.
AI rationale
Source directly confirms password submission to a fixed external endpoint and redirection of the Codex runtime to that endpoint. The absence of lifecycle hooks does not remove the concrete credential-exfiltration behavior reached by the advertised CLI flow.
Evidence
package.jsonbin/apolo-zenith-code.js~/.apolo-zenith-code/config.toml~/.apolo-zenith-code/token~/.apolo-zenith-code/auth.json~/.apolo-zenith-code/email
Network endpoints2
apolo-zenith-production.up.railway.appapolo-zenith-production.up.railway.app/v1
Decision evidence
public snapshotAI called this Malicious at 94.0% confidence as Malware with low false-positive risk.
Evidence for block
- The default API endpoint is a fixed Railway host controlled outside the declared OpenAI dependency chain.
- Its login flow prompts for an email and password and POSTs them to that endpoint.
- It stores the returned token as `OPENAI_API_KEY` in its private Codex home.
- Normal CLI execution configures Codex to use the external provider and launches the native CLI or downloads one via npx.
Evidence against
- No npm lifecycle scripts are declared.
- Credential collection is reached through an explicit `login` or `cadastrar` command, not at install time.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
UrlStrings
Source & flagged code
6 flagged · loading sourcebin/apolo-zenith-code.jsView file
5Source sends the broad process environment to a literal external destination.
L5:
L6: import { spawn } from "node:child_process";
L7: import { existsSync, mkdirSync, writeFileSync, readFileSync } from "fs";
...
L14:
L15: // __dirname equivalente em ESM
L16: const __filename = fileURLToPath(import.meta.url);
...
L92: try {
L93: const packageJsonPath = require.resolve(`${platformPackage}/package.json`);
L94: vendorRoot = path.join(path.dirname(packageJsonPath), "vendor");
...
L102: "bin",
L103: process.platform === "win32" ? "apolo-zenith-code.exe" : "apolo-zenith-code",
L104: );
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
bin/apolo-zenith-code.jsView on unpkg · L55L6: import { spawn } from "node:child_process";
L7: import { existsSync, mkdirSync, writeFileSync, readFileSync } from "fs";
High
Child Process
Package source references child process execution.
bin/apolo-zenith-code.jsView on unpkg · L5•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
bin/apolo-zenith-code.js:
import { existsSync, mkdirSync, writeFileSync, readFileSync } from "fs";
writeFileSync(cfgPath, cfg);
writeFileSync(cfgPath, cfg);
env.CODEX_HOME = APOLLO_HOME;
const rlmod = await import("node:readline/promises");
writeFileSync(path.join(APOLLO_HOME, "token"), token);
writeFileSync(
writeFileSync(path.join(APOLLO_HOME, "email"), json.email || email);
Findings
1 Critical6 High3 Medium2 Low
CriticalHardcoded Runtime Data Exfiltrationbin/apolo-zenith-code.js
HighChild Processbin/apolo-zenith-code.js
HighShell
HighCredential Redirect Persistencebin/apolo-zenith-code.js
HighSandbox Evasion Gated Capabilitybin/apolo-zenith-code.js
HighRuntime Package Installbin/apolo-zenith-code.js
HighSuspicious Dependency Evidencebin/apolo-zenith-code.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowFilesystem
LowUrl Strings
Affected versions and remediation
This report applies to apolo-zenith-code@1.9.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing apolo-zenith-code@1.9.2. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.