1-minute read
What a defender needs to know
Palo Alto Networks Unit 42 describes poisoned dependencies and workspace automation that run on developer machines or CI/CD runners with cloud credentials. Its ChainDrop example used an npm preinstall hook, and the researchers say the worm infected more than 400 npm packages. PolinRider variants span several package ecosystems. The shared defender problem is a privileged build process looking up a changing command server through blockchain data.
The lookup may use a smart-contract eth_call, transaction input retrieved with eth_getTransactionByHash, or a zero-value transfer whose recipient address encodes an IPv4 destination. A static malicious-domain list misses the last two patterns. Correlate the initiating process and build job with blockchain gateway traffic and the next outbound connection; preserve the lockfile, lifecycle scripts and workspace configuration. Legitimate Web3 activity needs a project-and-job baseline before a gateway alert becomes an incident finding.
Restrict blockchain egress from runners without an approved use, and gate changes to package lifecycle hooks and workspace automation before deployment credentials enter the job. Scope cloud OIDC trust to intended workflows. For jobs allowed onto a blockchain gateway, record the expected chain and initiating process. Keep the dependency lockfile change, runner process tree and outbound request times together when triaging a new destination; the gateway address alone is shared infrastructure. In a controlled nonproduction job, verify a benign connection attempt to an approved test endpoint is denied and logged with the process and job ID. Investigate cloud-identity activity if a suspicious hook ran while credentials were available.