oh-my-codex@0.21.41
Multi-agent orchestration layer for OpenAI Codex CLI
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe evaluation helper silently routes OPENAI_API_KEY to api.layofflabs.com for matching models by default. Because the key belongs to OpenAI and the user is not asked to select or confirm this separate endpoint, this is credential exfiltration.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs dist/scripts/eval/collect-astra-defaults.js with its default model configuration.
Impact
The user’s OpenAI API key is sent to a separate service, where it could be retained or misused.
Mechanism
For matching model names, the collector selects layofflabs and configures Codex to use OPENAI_API_KEY as that provider’s credential at api.layofflabs.com.
Attack narrative
When the evaluation helper runs with its defaults, it selects the layofflabs provider for matching internal models and configures Codex to use the user’s OPENAI_API_KEY at api.layofflabs.com. This sends an OpenAI credential to a separate service without an explicit provider selection.
AI rationale
The evaluation helper silently routes OPENAI_API_KEY to api.layofflabs.com for matching models by default. Because the key belongs to OpenAI and the user is not asked to select or confirm this separate endpoint, this is credential exfiltration.
Evidence
dist/evals/astra-defaults/collector.jsdist/scripts/eval/collect-astra-defaults.jsastra-defaults-records.json/tmp/codex-eval-*
Network endpoints2
api.layofflabs.comgithub.com
Decision evidence
public snapshotAI called this Malicious at 92.0% confidence as Malware with low false-positive risk.
Evidence for block
- The eval collector automatically selects the layofflabs provider for matching internal model names and uses OPENAI_API_KEY as its credential variable.
- The collector configures that provider with https://api.layofflabs.com/v1 and binds its env_key to OPENAI_API_KEY.
- The eval script includes astra-defaults in its default config list and passes the provider setting into the collector loop.
Evidence against
- The credential flow is in an evaluation helper that must be run explicitly; it is not triggered by package import or ordinary CLI startup.
- The postinstall hook is limited to global installs and hydrates the package’s native runtime.
- The hard-coded GitHub issue targets appear in smoke-test command probes, not automatic account actions.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
12 flaggedpackage.jsonView file
•scripts.postinstall = node -e "const fs=require('fs');const p='./dist/scripts/postinstall.js';if(fs.existsSync(p))import(p).then(m=>m.main?.()).catch(e=>console.warn('[omx] Postinstall skipped after a n...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "const fs=require('fs');const p='./dist/scripts/postinstall.js';if(fs.existsSync(p))import(p).then(m=>m.main?.()).catch(e=>console.warn('[omx] Postinstall skipped after a n...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgdist/cli/__tests__/detached-leader-teardown.test.jsView file
340patternName = github_fine_grained
severity = critical
line = 340
Findings
4 Critical5 High6 Medium5 Low
CriticalRed Install Lifecycle Scriptpackage.json
CriticalCritical Secretdist/cli/__tests__/detached-leader-teardown.test.js
CriticalPrevious Version Dangerous Deltadist/cli/index.js
CriticalSecret Patterndist/cli/__tests__/detached-leader-teardown.test.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/autoresearch/runtime.js
HighShelldist/autoresearch/runtime.js
HighRuntime Package Installdist/evals/astra-defaults/collector.js
HighSemantic Analysis Limiteddist/cli/api.js#virtual:normalized:round1
MediumDynamic Requiredist/cli/hooks.js
MediumNetwork
Affected versions and remediation
This report applies to oh-my-codex@0.21.41.
See all versions of oh-my-codex for other recorded verdicts.
- Avoid installing oh-my-codex@0.21.41. 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.