@mutmutco/codex-plugin@4.5.90
MMI workflow skills and org gates delivery.
AI Security Review
scanned 5d ago · by lpm-firewall-aiSource inspection confirms an existing GitHub credential is sent to a package-selected Hub endpoint without recipient-specific consent or destination validation. This is a credential disclosure risk and supports blocking publication, although it is triggered by CLI authentication rather than package installation.
Decision evidence
public snapshot- The CLI reads existing GitHub credentials from environment variables or the GitHub CLI.
- The Hub URL defaults to the product backend, but MMI_HUB_URL can redirect it; URL normalization only removes a trailing slash.
- When creating a Hub session, the CLI sends the GitHub token as a bearer credential to the configured endpoint’s session path.
- The whoami command reaches this session flow, and shared Hub requests use the same authentication helper.
- The package manifest declares no lifecycle scripts, so this exposure occurs when CLI authentication runs.
- The flagged agent-configuration path is used to classify untracked paths in clean-tree logic, not to write agent configuration.
- The credential transfer is part of runtime Hub authentication rather than an automatic npm install hook.
- The inspected agent-configuration path does not establish a separate attack surface.
Source & flagged code
7 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
cli/dist/main.cjsView on unpkg · L39This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
cli/dist/main.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @mutmutco/codex-plugin@4.5.90.
See all versions of @mutmutco/codex-plugin for other recorded verdicts.
- Avoid installing @mutmutco/codex-plugin@4.5.90. 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.