registry / @nalvietnam/avatar-cli / 3.21.0
@nalvietnam/avatar-cli@3.21.0
AI harness CLI for NAL Vietnam engineering
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install-time behavior was found: postinstall only displays a welcome screen. However, explicit commands install remotely delivered agent-pack content with non-enforcing integrity verification and can modify project AI configuration, warranting a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
User runs `avatar init`, `avatar sync`, or tools/AI setup commands.
Impact
A compromised or unsigned remote pack could influence the configured project agent environment.
Mechanism
Remote pack installation and project-scoped AI configuration merge.
AI rationale
No concrete malicious install-time behavior was found: postinstall only displays a welcome screen. However, explicit commands install remotely delivered agent-pack content with non-enforcing integrity verification and can modify project AI configuration, warranting a warning.
Evidence
package.jsonbin/postinstall.jsREADME.mddist/index.js.claude/pack/.claude/settings.json
Network endpoints1
qpdbkewtpkkbcrptnlos.supabase.co/functions/v1/get-pack
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- `avatar init`/`sync` downloads a remotely supplied team pack into `.claude/pack/`.
- The documented SHA-256 check is soft: installation continues when the backend omits a digest.
- CLI tool management merges pack manifests into project `.claude/settings.json`, an AI-agent control surface.
Evidence against
- The npm `postinstall` only loads a welcome-screen module and exits under CI/opt-out; it does not configure an agent surface.
- Pack download and configuration occur through explicit CLI commands, not package installation.
- No source evidence of credential harvesting, stealth exfiltration, remote code execution, or foreign/broad agent-config mutation was found.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsMinifiedUrlStrings
NoLicense
Source & flagged code
6 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
7`),plain:t=>process.stdout.write(`${t}
L8: `)}});var Kt={};ut(Kt,{atomicSwapDir:()=>ye,computeFileSha256:()=>yr,copyDirRecursive:()=>hr,downloadFile:()=>kr,ensureDir:()=>v,extractTarballToDir:()=>wr,pathExists:()=>g,readJso...
L9: `,n)}async function hr(t,e,n=[]){await v(e);let r=await D.readdir(t,{withFileTypes:!0});for(let o of r){if(n.includes(o.name))continue;let i=tn(t,o.name),c=tn(e,o.name);if(o.isDire...
High
Child Process
Package source references child process execution.
Findings
5 High4 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/index.js
HighSame File Env Network Executiondist/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
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @nalvietnam/avatar-cli@3.21.0.
See all versions of @nalvietnam/avatar-cli for other recorded verdicts.
- Review the evidence and your use of @nalvietnam/avatar-cli@3.21.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.