gitxelectron@1.3.2
An elegant, completely silent auto-syncing Git client. Works as a desktop app and npm CLI tool.
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe package contains a concrete unvalidated external-to-shell command path. This is a dangerous remote code execution capability, but the observed trigger is user-invoked rather than a covert install-time attack.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Run the push command, have it fail, and receive an AI response containing commands.
Impact
A compromised or prompt-injected AI response could execute arbitrary commands with the invoking user's permissions.
Mechanism
The CLI forwards Git error context to an AI provider and passes each returned command to synchronous shell execution.
AI rationale
The package contains a concrete unvalidated external-to-shell command path. This is a dangerous remote code execution capability, but the observed trigger is user-invoked rather than a covert install-time attack.
Evidence
package.jsonbin/postinstall.jsbin/cli.jsout/main/index.js
Network endpoints1
router.huggingface.co/v1
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The package defines automatic preinstall and postinstall hooks.
- Global installation launches a detached Electron application without an explicit command from the user.
- The push error handler sends repository state to an AI service and executes every returned command through a shell.
- The desktop update handler starts a detached Windows command that installs the latest versions of two packages globally.
Evidence against
- The AI command path is reached only after a user invokes the push command and that operation fails.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
10 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
3 Critical6 High4 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationout/main/index.js
CriticalDownload Executeout/main/index.js
CriticalTrigger Reachable Dangerous Capabilityout/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
MediumNetwork
MediumEnvironment Vars
Affected versions and remediation
This report applies to gitxelectron@1.3.2.
See all versions of gitxelectron for other recorded verdicts.
- Review the evidence and your use of gitxelectron@1.3.2 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.