@yuandc/aica@0.1.80

AICA remote Agent worker

AI Security Review

scanned 8d ago · by lpm-firewall-ai

The manifest and runtime behavior are consistent with a user-started remote agent worker that uses local Codex tools and communicates with its configured ACA service. Login credentials are supplied for that service, and the insecure TLS option is guarded by an affirmative opt-in; no concrete attack was established.

Static reason

One or more suspicious static signals were detected.

Trigger

A user invokes the CLI; login and worker network activity occur as part of the selected command.

Impact

The inspected behavior showed no hidden installation activity, unrelated credential transfer, or unsolicited account action.

Mechanism

The worker communicates with its configured ACA service and local Codex tools. TLS certificate checks are bypassed only after an affirmative environment opt-in.

AI rationale

Network endpoints1

aca.kinghon.com.cn:8843/

Decision evidence

public snapshot

AI called this Clean at 96.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json exposes the CLI and only start/help scripts; the CLI dispatches commands when invoked.
The flagged Codex path logic searches local installation paths and launches a local Codex process or app server.
Codex session and provider helpers use local app-server requests, while the worker handles explicit service operations.
Starting the worker sends machine, project, and provider presence to the configured ACA service; heartbeat sending requires a saved token.
Login sends entered credentials to the selected or default ACA service. Certificate checks are bypassed only when ACA_SERVER_INSECURE_TLS is affirmatively enabled.
Interactive Bash setup writes an app-specific rc file and passes it with --rcfile; it does not modify shell profiles.

Evidence against

Behavioral surface

Source

ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork

Supply chain

HighEntropyStrings

Source & flagged code

3 flagged

dist/core/terminal/shell.jsView file

2Trigger-reachable persistence chain: scripts.start -> dist/worker-cli.js -> dist/commands/start.js -> dist/core/machine-filesystem-worker.js -> dist/core/terminal/service.js -> dist/core/terminal/shell.js L2: __aca_terminal_initial_ps1=\${PS1-} L3: if [[ -r "$HOME/.bashrc" ]]; then L4: . "$HOME/.bashrc" ... L18: unset __aca_terminal_initial_ps1 L19: `;function $(o,l=process.env){const t={...l,TERM:"xterm-256color",COLORTERM:"truecolor"};if(process.platform==="win32"||a.basename(o)!=="bash")return{args:[],env:t};const n=a.join(...

High

Trigger Reachable Persistence

A manifest entrypoint or package-local install chain reaches persistence behavior.

dist/core/terminal/shell.jsView on unpkg · L2

2__aca_terminal_initial_ps1=\${PS1-} L3: if [[ -r "$HOME/.bashrc" ]]; then L4: . "$HOME/.bashrc" ... L18: unset __aca_terminal_initial_ps1 L19: `;function $(o,l=process.env){const t={...l,TERM:"xterm-256color",COLORTERM:"truecolor"};if(process.platform==="win32"||a.basename(o)!=="bash")return{args:[],env:t};const n=a.join(...

Medium

Install Persistence

Source writes installer persistence such as shell profile or service configuration.

dist/core/terminal/shell.jsView on unpkg · L2

dist/core/aca-config.js

Findings

2 High5 Medium5 Low

HighSandbox Evasion Gated Capabilitydist/core/aca-config.js

HighTrigger Reachable Persistencedist/core/terminal/shell.js

MediumDynamic Require

MediumNetwork

MediumEnvironment Vars

MediumInstall Persistencedist/core/terminal/shell.js

MediumStructural Risk Force Deep Review

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

LowUrl Strings

LowNo License

Affected versions and remediation

This report applies to @yuandc/aica@0.1.80.

See all versions of @yuandc/aica for other recorded verdicts.

Review the evidence and your use of @yuandc/aica@0.1.80 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: 2026-10-20 05:29:09.133Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.