Which versions of geocode-quick are malicious?

The following npm versions of geocode-quick are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate geocode-quick if I installed it?

geocode-quick 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.

I already installed geocode-quick — how do I know if it already compromised me?

If geocode-quick was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is geocode-quick part of a known attack campaign?

Yes — geocode-quick is associated with the IN-MAL-2026-014619, IN-MAL-2026-015836 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find geocode-quick across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for geocode-quick (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging geocode-quick across your stack and pipelines.

Malicious package

geocode-quicknpm

geocode-quick is a confirmed malicious npm package (MAL-2026-12180) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.2, 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in geocode-quick (npm)

MAL-2026-12180

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall geocode-quick

What this malware does

The package advertises itself as a geocoding CLI but, on every invocation of the tool, executes env via execFile to dump the full process environment and POSTs the output to the hardcoded endpoint https://ssc.catwealth.net alongside each geocode record. The shell command string (env) and the JSON payload field (key) are encoded using unicode escapes interleaved with zero-width and whitespace characters that are stripped at runtime, hiding the exfiltration from static/grep review. Cover-story identifiers (captureAuxOutput, SECRET_KEY_FIELD, AUX_CMD) further disguise the behavior. Push behavior is on by default; opt-out requires an explicit --no-push flag. Process environment on developer and CI hosts routinely contains API keys, cloud credentials, and CI secrets, all of which are shipped to the attacker-controlled destination.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

f7380008cb8f1ca7e634cb4389ea9d8f02b5ef552b44746770ba8f1798137c5a

92f8f109952f61867c1ca8819f7a151b89de305ff4b157f49400ef4428019419

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for geocode-quick (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging geocode-quick across your stack and pipelines.
If you installed it — respond
geocode-quick 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.
Did it already run?
If geocode-quick was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks geocode-quick before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. geocode-quick on npm has been identified as a malicious package (versions 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014619IN-MAL-2026-015836

References

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database