registry / Remote code execution / gitelectron
gitelectron
An elegant, completely silent auto-syncing Git client. Works as a desktop app and npm CLI tool.
This report shows the evidence for gitelectron@1.0.16. 3 of 14 known versions are blocked or flagged. The newest version, 1.0.17, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete arbitrary-command execution path fed by a remote AI response, plus intrusive lifecycle behavior. This exceeds normal Git-client functionality and creates a practical remote code execution risk.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Run the push command and cause a Git error; install the package.
Impact
A compromised, malicious, or prompt-injected AI response can execute arbitrary commands with the user's privileges and receive repository metadata.
Mechanism
Unvalidated remote AI command execution and install-time process launch.
Attack narrative
When the push command fails, the CLI serializes Git status and the error message into an AI prompt. It accepts the returned commands and passes each directly to execSync without an allowlist, confirmation, or sandbox. Repository-controlled content or a compromised AI endpoint can therefore turn a routine Git error into arbitrary local command execution. The install hook independently runs npx and may launch a detached GUI process.
AI rationale
The package contains a concrete arbitrary-command execution path fed by a remote AI response, plus intrusive lifecycle behavior. This exceeds normal Git-client functionality and creates a practical remote code execution risk.
Evidence
package.jsonbin/cli.jsbin/postinstall.jsbin/preuninstall.jsout/main/index.js
Network endpoints2
router.huggingface.co/v1models.inference.ai.azure.com
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The CLI sends Git status and error text to an external AI service, then executes every returned command without validation.
- The package includes hard-coded fallback AI credentials in CLI and desktop code.
- Its postinstall hook runs an npx command and globally installed packages automatically launch a detached Electron application.
- The preinstall hook force-terminates processes whose command line matches GitElectron.
Evidence against
- The desktop application's GitHub OAuth and API calls are consistent with a Git client.
- GitHub account tokens are stored using Electron safe storage encryption.
- No evidence shows harvesting arbitrary local files or sending GitHub tokens to an unrelated host.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 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/postinstall.jsView file
2L3: const { spawn } = require('child_process')
L4: const path = require('path')
High
46
Findings
6 High4 Medium5 Low
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 Similarityout/main/index.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to gitelectron@1.0.16.
The versions list below shows the verdict for each recorded version.
- Avoid installing gitelectron@1.0.16. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.