registry / @nalvietnam/avatar-cli / 3.40.0
@nalvietnam/avatar-cli@3.40.0
AI harness CLI for NAL Vietnam engineering
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe inspected lifecycle hook only displays a welcome screen. The credential and workspace configuration behavior is part of explicit provider setup, and the inspected agent-related excerpt only detects Avatar workspace files; no concrete attack behavior was established.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation triggers the postinstall welcome screen; explicit CLI use triggers AI provider setup.
Impact
No unauthorized credential transfer, foreign agent configuration mutation, or other attack effect was established in these paths.
Mechanism
The postinstall script imports and calls the welcome-screen function. AI setup prompts for a provider and key, verifies the key with the selected endpoint, and saves provider configuration for the workspace.
AI rationale
The inspected lifecycle hook only displays a welcome screen. The credential and workspace configuration behavior is part of explicit provider setup, and the inspected agent-related excerpt only detects Avatar workspace files; no concrete attack behavior was established.
Evidence
package.jsonbin/postinstall.jsdist/index.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The install hook runs a script that displays a welcome screen, with no source evidence of credential transfer or configuration changes during installation.
- The CLI offers an explicit provider choice and prompts for a key before configuring an AI provider.
- The LLMLite key is verified against the selected base URL, then the chosen provider settings are written for the selected workspace.
- The agent-related path identifies Avatar workspace configuration files; the inspected excerpt shows path detection, not a write to foreign agent settings.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedPossibleObfuscationTelemetryUrlStrings
NoLicense
Source & flagged code
8 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node ./bin/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node ./bin/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/index.jsView file
10`),plain:e=>Vs(`${e}
L11: `)}});var Yr={};gt(Yr,{atomicSwapDir:()=>qs,computeFileSha256:()=>Ks,copyDirRecursive:()=>Ws,downloadFile:()=>ag,ensureDir:()=>S,extractTarballToDir:()=>cg,pathExists:()=>k,readJso...
L12: `,n)}async function Ws(e,t,n=[]){await S(t);let r=await Te.readdir(e,{withFileTypes:!0});for(let o of r){if(n.includes(o.name))continue;let i=Rd(e,o.name),s=Rd(t,o.name);if(o.isDir...
High
Child Process
Package source references child process execution.
Findings
7 High4 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/index.js
HighShelldist/index.js
HighSame File Env Network Executiondist/index.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/index.js
HighTrigger Reachable Command Output Exfiltrationdist/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
Affected versions and remediation
This report applies to @nalvietnam/avatar-cli@3.40.0.
See all versions of @nalvietnam/avatar-cli for other recorded verdicts.
- Review the evidence and your use of @nalvietnam/avatar-cli@3.40.0 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.