Which versions of gogets.dev/btreex are malicious?

Every published version of gogets.dev/btreex on Go is considered malicious. Remove the package entirely.

How do I remediate gogets.dev/btreex if I installed it?

gogets.dev/btreex 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 gogets.dev/btreex — how do I know if it already compromised me?

If gogets.dev/btreex 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.

How do I find gogets.dev/btreex across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gogets.dev/btreex (all published versions).

Malicious package

gogets.dev/btreexGo

Advisory published Oct 2, 2026Updated Oct 2, 2026

gogets.dev/btreex is a confirmed malicious Go package (MAL-2026-17454) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gogets.dev/btreex (Go)

MAL-2026-17454

Immediate action

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

remove gogets.dev/btreex

What this malware does

Part of the Graphalgo campaign. The module, first published around 2026-09-08, hides its payload in a ZIP archive disguised as a SQL file (btreex.sql). The payload is triggered when a specific price integer value is passed, and drops the same dual-channel RAT (Ethereum smart contract dead drop plus Slack bot token) used by gocommunity.io/orderedbtree.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gogets.dev/btreex (all published versions).
If you installed it — respond
gogets.dev/btreex 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 gogets.dev/btreex 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. gogets.dev/btreex on Go has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

aikido.dev

Credits

Aikido Security · finder

Detect & block this

O3 blocks gogets.dev/btreex-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