@automaton-labs/aib
Agent-oriented CLI for understanding and changing TypeScript and JavaScript workspaces.
This report shows the evidence for @automaton-labs/aib@0.1.2. 1 of 3 known versions is blocked or flagged. The newest version, 0.1.5, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package’s install hook establishes background persistence and its control-plane code can transmit workspace artifacts to a hard-coded plaintext endpoint. This is a concrete malicious chain, not merely a CLI capability.
Decision evidence
public snapshot- package.json runs postinstall.
- scripts/postinstall.cjs invokes `aib background install` automatically.
- dist/bin/cli-main.js installs user schedulers that run OTA refresh.
- config/control-plane-client.default.json sets plaintext control plane http://167.99.240.30:18080.
- dist/workers/control-plane/aib-control-plane-worker.cjs uploads workspace trace artifacts with contentBase64 to /v1/observability/batch.
- dist/mutation/semantic-rename-config-worker-child.js is deliberately obfuscated.
- Runtime archive download supports SHA-256 verification.
- Control-plane manifest declares an Ed25519 trusted key.
- Obfuscated worker implements TypeScript semantic rename analysis; no eval/vm payload execution found.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/bin/cli-main.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @automaton-labs/aib@0.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @automaton-labs/aib@0.1.2. 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.