Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

pushgitquickxnpm

Advisory published Updated

pushgitquickx is a confirmed malicious npm package (MAL-2026-14578) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.4, 1.0.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pushgitquickx (npm)

MAL-2026-14578
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pushgitquickx

What this malware does

The push subcommand of this CLI catches exceptions from git operations and, in the error handler, sends the git error text and JSON-serialized git status output (branch name, tracked and untracked file paths, ahead/behind info) to Google Gemini via the @google/generative-ai SDK using a Google API key hardcoded in the source. The model's response includes a commandsToRun array, and the code iterates that array and executes each string via execSync on the installer's machine with stdio: 'ignore' (for (const cmd of aiResponse.commandsToRun) { execSync(cmd, { stdio: 'ignore' }); }). Because the remote model is conditioned on attacker-influenceable inputs (branch names, file paths, error strings coming from arbitrary repository state) and any command it emits is run without confirmation, allow-listing, or logging, this is a remote-controlled shell-execution surface on the installer's host — running gitquickpush push inside a repo whose contents can steer the model output can result in arbitrary command execution, including destructive git operations or broader host commands. The AI phone-home is also undisclosed in the README, and the git-status payload sent to Google is routed through the author's own hardcoded Gemini API key rather than a caller-configured credential, so the caller does not choose the destination. The same source additionally embeds the author's Google generative-language API key in plaintext, exposing the author's own quota.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

15 flagged
1.0.01.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.121.0.131.0.141.0.151.0.161.0.17

Indicators of compromise (SHA-256)

30471d92246bb45583fa030ec8ed294c517bbaae3542809a402b7f78faa29fc0
35dc3f684a8497c65e595e4a43516bf7927f4057318de0c4790f167c6e471ed7
40d7ca6dda3f848a779ea513a1236d948f44d184b09be360c2daeb85c2652b5e
557f230f5bf78b909b207a6568053a346e32a2fcbd14130a824bd6de8fc7fbf6
9d3872078c559651efca15359db5a3e83ccda8e49bc774d0bc942bf9d4436c25

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for pushgitquickx (15 malicious versions).

  2. If you installed it — respond

    pushgitquickx is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If pushgitquickx was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pushgitquickx on npm has been identified as a malicious package (versions 1.0.0, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.0.10, and 7 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wx29-h78g-ww4fIN-MAL-2026-019167IN-MAL-2026-019168IN-MAL-2026-019170IN-MAL-2026-019169

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks pushgitquickx-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

pushgitquickx (npm) malicious package — MAL-2026-14578 | O3 Security