@microwiseai/snapshot@0.7.0
CLI for installing IST Snapshot packages
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe explicit install flow sends the user’s email and account identifier to the vendor’s telemetry endpoint, along with a prefix of the auth token. This is suspicious runtime telemetry, though the reviewed source does not show a full credential being transmitted.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
After a user runs the snapshot install command.
Impact
The vendor receives the user’s email and account identifier, plus a token prefix. This is a privacy and credential-material exposure concern, but the source does not show the full token being sent.
Mechanism
The command reads IST credentials and includes the user ID, email, and first nine auth-token characters in a fire-and-forget telemetry request.
AI rationale
The explicit install flow sends the user’s email and account identifier to the vendor’s telemetry endpoint, along with a prefix of the auth token. This is suspicious runtime telemetry, though the reviewed source does not show a full credential being transmitted.
Evidence
dist/commands/install.jsdist/lib/config.js~/.ist/credentials.json
Network endpoints1
license-api.sisung-kim1.workers.dev/api/telemetry
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The CLI sends fire-and-forget telemetry when an install command completes.
- The telemetry includes the IST user ID, email, and the first nine characters of the auth token.
- Telemetry is POSTed to LICENSE_API_URL/telemetry, which defaults to the package vendor’s license API.
Evidence against
- Telemetry runs after an explicit snapshot install command, not from an npm lifecycle hook.
- The destination defaults to the vendor’s license API, and the code sends only a token prefix rather than the full token.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/lib/install-verify.jsView file
1import { execSync } from 'child_process';
L2: import { existsSync, readFileSync } from 'fs';
High
Child Process
Package source references child process execution.
dist/lib/install-verify.jsView on unpkg · L1dist/commands/publish.jsView file
66return new Promise((resolve, reject) => {
L67: // NO shell:true. With a shell, /bin/sh -c would re-parse the joined argv and
L68: // a value like --bump 'patch; touch /tmp/pwn' could split the command,
High
node_modules/@microwiseai/license/dist/machine/instance.jsView file
Findings
1 Critical4 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/lib/skit-adapter.js
HighChild Processdist/lib/install-verify.js
HighShelldist/commands/publish.js
HighRuntime Package Installnode_modules/@microwiseai/skit/dist/lib.js
HighSemantic Analysis Limiteddist/lib/version-validator.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptonode_modules/@microwiseai/license/dist/machine/instance.js
LowFilesystem
LowHigh Entropy Strings
Low
Affected versions and remediation
This report applies to @microwiseai/snapshot@0.7.0.
See all versions of @microwiseai/snapshot for other recorded verdicts.
- Review the evidence and your use of @microwiseai/snapshot@0.7.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.