DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
HighAdvisory sweepGo0 affected versions

gocommunity.io/orderedbtree

gocommunity.io/orderedbtree has 0 versions on the Go module proxy flagged in 2 incidents we track. Only the exact versions listed below were named by the source advisories.

gocommunity.io/orderedbtree was recorded in a daily advisory sweep. The write-up groups it into a cluster with the evidence available at the time; check the cluster note before treating it as a confirmed compromise.

Affected versions

Check what you actually have installed with go list -m all.

    The 2 incidents that flagged it

    High

    GitHub Advisory malware sweep - 2026-10-02 (late) + 2026-10-03 (npm `amel10` AWS API Gateway dep-confusion mass push targeting Amazon/Alexa internal names - 6 confirmed packages sharing C2 `s85r5k14qk.execute-api.us-east-1.amazonaws.com`: `alexa-cybertron-team-code-review-agent`, `okra-cloud-cdk`, `ai-workshop-radio-app`, `ai-workshop-maa15-radio`, `ai-workshop-radio-lambda`, `niksinnkatalapp`; 5 npm PhantomSub Baileys silent WhatsApp follow siblings `mikuhostt-baileys`, `luoxy-baileys`, `@zanta/baileys`, `wailib`, `prastzy`; pip `dedh-devops-automation` AWS Lambda + Secrets Manager credential theft `spo365-graph` family continuation; pip `voxeval` cryptominer NEW campaign `2026-10-voxeval`; 2 Go module `Graphalgo` campaign expansion `gogets.dev/btreex`, `gocommunity.io/orderedbtree`; npm `@bluewin/utils` Burp-Collaborator Swisscom-scope dep-confusion probe by `securityresearch1`; npm `@smwebserver/static@99.9.1` sentinel-version malicious-domain beacon; 9 npm CWE-506 boilerplate takedowns `turbo-ws`, `hardhat-zet`, `ui-base-colors`, `translate-base-font`, `ui.dist.min.js`, `@woodpecker-web-shared/components`, `bnppf-flag-icons`)

    GHSA 2026-10-02 (late) + 2026-10-03: ~26 new advisories. Confirmed payloads: 6-package amel10 npm dep-confusion mass push against Amazon/Alexa internal names (shared C2 s85r5k14qk.execute-api.us-east-1.amazonaws.com); 5 PhantomSub Baileys siblings (query ID 7871414976211147); pip dedh-devops-automation AWS Lambda credential theft (spo365-graph family day 2); pip voxeval cryptominer; 2 Go modules in the Graphalgo campaign.

    Versions named here:

    High

    Lazarus "graphalgo" fake-recruiter campaign (npm + PyPI + Go)

    ReversingLabs attributed an ongoing fake-recruiter campaign (active since May 2025, reported Feb 2026) to North Korea's Lazarus Group (overlapping Jade Sleet / UNC4899). Crypto, JavaScript, and Python developers are lured via LinkedIn/Reddit/Facebook into interview "coding tasks" that pull a token-protected RAT loader from npm and PyPI. ~192 malicious packages attributed in total; bigmathutils alone passed 10,000 downloads.

    Versions named here:

    What to do if you installed one of these

    Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

    1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
    2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
    3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
    4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

    Check your whole project

    gocommunity.io/orderedbtree is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse Go manifests yet, but the incident write-ups list every affected package.

    Browse the incident feed All flagged Go packages

    Other packages in the same incident

    If gocommunity.io/orderedbtree is in your tree, these are worth checking too - they were published by the same campaign.

    See the full incident

    Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.