@aui.io/apollo@0.1.95
Apollo CLI — author, test and operate Apollo-1 agents from your terminal (scriptable CLI + interactive TUI)
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe postinstall persistently modifies user shell startup files without an affirmative setup step, so this warrants a warning. The wrapper's behavior is scoped to Apollo's agent workflow, and the inspected source does not establish a concrete malicious attack.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package with lifecycle scripts enabled.
Impact
Future shell sessions invoke the Apollo wrapper, which can change directories after specified Apollo agent commands.
Mechanism
The postinstall script appends an Apollo shell-init evaluation command to applicable zsh/bash startup files; future shells load the wrapper when Apollo is available.
AI rationale
The postinstall persistently modifies user shell startup files without an affirmative setup step, so this warrants a warning. The wrapper's behavior is scoped to Apollo's agent workflow, and the inspected source does not establish a concrete malicious attack.
Evidence
package.jsonscripts/setup-shell.mjsnode_modules/@aui.io/apollo-cli/dist/src/commands/shell.js.zshrc.bashrc.bash_profile
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json runs scripts/setup-shell.mjs during postinstall.
- The setup script appends a command to evaluate Apollo's shell wrapper in user startup files.
- The script targets existing zsh/bash startup files and can create the detected login shell's file.
- The setup runs automatically unless CI or APOLLO_NO_SHELL_SETUP disables it.
- The wrapper limits automatic directory changes to successful Apollo agent use, import, or create commands.
Evidence against
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystem
NoLicense
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node ./scripts/ensure-opentui.mjs && node ./scripts/setup-shell.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./scripts/ensure-opentui.mjs && node ./scripts/setup-shell.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/apollo.jsView file
10L11: const require = createRequire(import.meta.url);
L12: const cliBin = require.resolve("@aui.io/apollo-cli/bin/apollo.js");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
bin/apollo.jsView on unpkg · L10Findings
7 High5 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitednode_modules/@aui.io/apollo-core/node_modules/diff/dist/diff.min.js#virtual:normalized:round1
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-cli/node_modules/commander/lib/command.js
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-tui/dist/src/lib/ide.js
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-tui/node_modules/@opentui/core/chunk-bun-t2myhmwd.js
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-tui/dist/src/author/backend/claudeCode.js
HighPrevious Version Dangerous Deltanode_modules/@aui.io/apollo-cli/dist/src/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/apollo.js
Affected versions and remediation
This report applies to @aui.io/apollo@0.1.95.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.95 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.