Research, engineering, product guides, and field reports from the Garnet team.
In five supply-chain incidents reported in March 2026, the diff and the lockfile named a version but not what it ran. What a recorded CI run adds to review: execution chains ending in outbound connections, attributed to the process that made them.
Garnet TeamResearchPosts from real CI runs: the execution chains behind each outbound connection, read from the Execution Profile.
Execution Profile for npm install @tanstack/react-router@1.169.8, run 25697800810. The lockfile named one package version; the recorded run shows the install starting a Bun binary from the npm cache that connected to git-tanstack.com, api.github.com and the cloud metadata address.
Self-deleting postinstall dropper; the Execution Profile is the only durable evidence of what ran.
.pth startup hook drops to a shell and runs credential-harvest commands before any import.
Green Trivy scan beside a sibling branch scraping /proc/<pid>/mem — both in one workflow tree.
KICS scan logs looked routine while a parallel branch reached checkmarx[.]zone.
import telnyx spawns a child, opens C2 egress, and reparents to systemd(1) before the step ends.
One compromised npm install pivots Node→Bun and attempts rogue runner registration end to end.
Technical deep-dives into Garnet's architecture and runtime engine.
