@yuandc/aica@0.1.58
AICA remote Agent worker
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe flagged persistence and platform checks resolve to private terminal initialization and ordinary path handling. Inspected execution and authentication behavior is consistent with an explicitly started remote agent worker, with no concrete malicious chain established.
Decision evidence
public snapshot- package.json has only start and help scripts, no install lifecycle hooks or runtime self-dependency.
- dist/core/aca-config.js uses platform checks to normalize project paths, not to conceal execution.
- dist/core/terminal/shell.js writes a private terminal startup file under the AICA home and passes it through Bash's rcfile option.
- dist/core/terminal/service.js implements interactive shell sessions; terminal/worker.js connects to the configured server with its authentication token.
- dist/commands/start.js activates the worker through an explicit CLI action.
- dist/commands/worker-auth.js obtains the worker token from login to the selected server and stores that server alongside the token.
Source & flagged code
4 flaggedA manifest entrypoint or package-local install chain reaches persistence behavior.
dist/core/terminal/shell.jsView on unpkg · L2Source writes installer persistence such as shell profile or service configuration.
dist/core/terminal/shell.jsView on unpkg · L2Findings
Affected versions and remediation
This report applies to @yuandc/aica@0.1.58.
See all versions of @yuandc/aica for other recorded verdicts.
- Review the evidence and your use of @yuandc/aica@0.1.58 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.