gitxelectron@1.3.8
An elegant, completely silent auto-syncing Git client. Works as a desktop app and npm CLI tool.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe update action silently includes a second global package installation, creating a meaningful user-invoked code execution risk. The inspected source does not establish malicious behavior or an npm lifecycle attack, so this warrants a warning rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A user invokes the app's install-update action.
Impact
This can execute package lifecycle code and add or replace globally available software on the user's machine.
Mechanism
A detached Windows command runs npm's global installer for both package names and then starts the app again.
AI rationale
The update action silently includes a second global package installation, creating a meaningful user-invoked code execution risk. The inspected source does not establish malicious behavior or an npm lifecycle attack, so this warrants a warning rather than a block.
Evidence
out/main/index.js
Network endpoints1
registry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The app exposes an update action that launches a detached Windows command to install gitelectron@latest and gitquickpush-cli@latest globally.
- The update command starts a new shell and exits the current Electron app, so installation is automatic once that action is invoked.
- The package lifecycle hooks run a dependency setup command and launch the app only for global installs; inspected code does not show them installing the extra CLI.
Evidence against
- The extra global installation is reached through the app's explicit install-update action, not an npm install lifecycle hook.
- The package's app and CLI otherwise use expected GitHub and model-service endpoints for Git and AI-assisted features.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 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 unpkgbin/auto-push.jsView file
17const crypto = require('crypto')
L18: const { spawnSync, spawn } = require('child_process')
L19:
High
14
Findings
4 Critical5 High5 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationout/main/index.js
CriticalDownload Executeout/main/index.js
CriticalTrigger Reachable Dangerous Capabilityout/main/index.js
CriticalPrevious Version Dangerous Deltabin/cli.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/auto-push.js
HighShellbin/postinstall.js
HighRuntime Package Installbin/postinstall.js
HighKnown Malware Source Similaritybin/postinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requirebin/auto-push.js
MediumNetwork
Affected versions and remediation
This report applies to gitxelectron@1.3.8.
See all versions of gitxelectron for other recorded verdicts.
- Review the evidence and your use of gitxelectron@1.3.8 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.