@aui.io/apollo@0.1.41
Apollo operator console — CLI + interactive TUI
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe automatic postinstall change to user shell startup files is a real persistence risk, so this merits a warning. The inspected source does not establish a concrete malicious chain or a reason to block publication.
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 outside CI without setting APOLLO_NO_SHELL_SETUP=1.
Impact
Apollo shell initialization runs on later shell starts, creating a persistent user-level change; the inspected code does not establish malicious payload execution or data theft.
Mechanism
The setup script appends a guarded eval command to existing zsh/bash startup files and may create the login shell’s startup file.
AI rationale
The automatic postinstall change to user shell startup files is a real persistence risk, so this merits a warning. The inspected source does not establish a concrete malicious chain or a reason to block publication.
Evidence
package.jsonscripts/setup-shell.mjs~/.zshrc~/.bashrc~/.bash_profile
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs shell setup automatically from its postinstall hook.
- That setup appends a command to existing shell startup files and may create the login shell’s startup file.
- The appended command evaluates Apollo’s shell initialization whenever the shell starts.
Evidence against
- The setup skips CI and supports an explicit APOLLO_NO_SHELL_SETUP=1 opt-out.
- The setup is idempotent, reports the files it changes, and describes the added integration.
- The other install helper is gated on missing OpenTUI files and reinstalls the package-declared OpenTUI dependencies.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemShell
NoLicense
Source & flagged code
15 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
12 High5 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSemantic Analysis Limitednode_modules/@aui.io/apollo-core/node_modules/yaml/dist/parse/lexer.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-core/dist/src/services/doctor.js
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-tui/dist/src/lib/ide.js
HighKnown Malware Source Similaritynode_modules/@aui.io/apollo-core/dist/src/api/identity.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-core/dist/src/services/upgrade.js
Affected versions and remediation
This report applies to @aui.io/apollo@0.1.41.
See all versions of @aui.io/apollo for other recorded verdicts.
- Review the evidence and your use of @aui.io/apollo@0.1.41 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.