gitxelectron@1.3.7
An elegant, completely silent auto-syncing Git client. Works as a desktop app and npm CLI tool.
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource confirms automatic execution of unvalidated AI-generated shell commands, warranting a warning for remote code execution risk. The scanner's malicious labels are not supported by separate concrete attack evidence in the inspected source.
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 runs the CLI push command and the operation fails.
Impact
A manipulated model response could execute arbitrary commands with the user's permissions and modify or expose local data.
Mechanism
Git status and error text enter an AI prompt; returned command strings reach execSync without validation or approval.
AI rationale
Source confirms automatic execution of unvalidated AI-generated shell commands, warranting a warning for remote code execution risk. The scanner's malicious labels are not supported by separate concrete attack evidence in the inspected source.
Evidence
bin/cli.js
Network endpoints1
router.huggingface.co/v1
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- bin/cli.js automatically executes AI-returned commands through execSync after a user-invoked push fails, without command validation or confirmation.
- bin/cli.js sends Git status and error text to an AI model, allowing untrusted repository or error content to influence executable commands.
- package.json activates install scripts; bin/postinstall.js can launch the Electron app during global installation.
- The inspected desktop command handler in out/main/index.js passes arguments to Git rather than executing arbitrary shell text.
Evidence against
- The risky CLI behavior implements Git error repair; inspected source does not establish malicious intent or a hidden attacker-controlled receiver.
- The manifest has no runtime self-dependency, and inspected lifecycle scripts perform dependency setup, app launch, shortcut creation, and process shutdown.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Source & flagged code
11 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./bin/preuninstall.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/postinstall.jsView file
2L3: const { spawn } = require('child_process')
L4: const path = require('path')
High
46
Findings
4 Critical6 High4 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationout/main/index.js
CriticalDownload Executeout/main/index.js
CriticalTrigger Reachable Dangerous Capabilityout/main/index.js
CriticalPrevious Version Dangerous Deltaout/main/index.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/postinstall.js
HighShellbin/postinstall.js
HighRuntime Package Installbin/postinstall.js
HighKnown Malware Source Similaritybin/cli.js
HighKnown Malware Source Similaritybin/postinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
Medium
Affected versions and remediation
This report applies to gitxelectron@1.3.7.
See all versions of gitxelectron for other recorded verdicts.
- Review the evidence and your use of gitxelectron@1.3.7 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.