@extenshi/cli@0.38.1
Pre-publish security scanner for browser extensions
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends default-on runtime usage telemetry even when a non-interactive run skips the consent prompt. The observed payload is limited, and no malicious credential handling or unrelated account actions were identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A CLI command is invoked; in CI or another non-interactive context, the consent question is skipped while event capture still runs.
Impact
Usage metadata may leave the machine without the user seeing the consent prompt for that run; no credential or project-content exfiltration was identified.
Mechanism
Telemetry sends command events and coarse runtime metadata to PostHog. The user can disable it with environment settings or saved preferences.
AI rationale
The package sends default-on runtime usage telemetry even when a non-interactive run skips the consent prompt. The observed payload is limited, and no malicious credential handling or unrelated account actions were identified.
Evidence
dist/telemetry.jsdist/telemetry-consent.jsdist/command-lifecycle.jsscripts/postinstall.cjs~/.extenshi/config.json
Network endpoints1
eu.i.posthog.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Runtime telemetry remains enabled unless the user opts out or saved settings disable it.
- The consent question is only asked in an interactive terminal, but commands capture telemetry after that question attempt regardless.
- The install hook sends an install event only when the config already records telemetry as true.
- Runtime telemetry is sent to eu.i.posthog.com.
Evidence against
- The interactive prompt describes anonymous usage reporting and offers a telemetry off command.
- The install hook's payload is limited to an anonymous ID, package version, Node version, OS, architecture and install metadata.
- The inspected credential-bearing requests use the configured Extenshi API endpoint for product commands.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
11 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.cjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/login-runtime.jsView file
11*/
L12: import { spawn } from 'node:child_process';
L13: import http from 'node:http';
High
Child Process
Package source references child process execution.
dist/login-runtime.jsView on unpkg · L11Findings
1 Critical6 High5 Medium9 Low
CriticalPrevious Version Dangerous Deltadist/screenshots.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/login-runtime.js
HighShelldist/analytics-init.js
HighSame File Env Network Executiondist/analytics-init.js#virtual:normalized:round1
HighRuntime Package Installdist/amo-source.js
HighSemantic Analysis Limiteddist/analytics-init.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/screenshots.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @extenshi/cli@0.38.1.
See all versions of @extenshi/cli for other recorded verdicts.
- Review the evidence and your use of @extenshi/cli@0.38.1 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.