When IP Whitelisting Isn't What It Seems: A Real-World Case Study from the Binance API
An architectural trust-boundary issue in the world's largest crypto exchange.

Search for a command to run...
Series
Technical security write-ups covering malware, abuse, impersonation, supply-chain risks, and real-world trust boundary failures.
An architectural trust-boundary issue in the world's largest crypto exchange.

Update (2026-04-22): Further analysis indicates that this fraudulent repository is likely one lure within a broader GitHub malware campaign.Across the currently confirmed set, multiple repositories sh

Update (2026-04-22, 13:33): I submitted this case to GitHub Support for campaign-level review. Ticket ID: 4313391. Further update (2026-04-23): I published a deeper technical follow-up covering the

How 19 fake GitHub repositories across 17 accounts led from a Python dropper to a StealC-linked payload chain.

A fake recruiter tried to turn VSCode workspace trust into silent code execution. Here is the attack chain, the infrastructure, and the IOCs.

A near-identical clone of my Binance WebSocket library had no payload — but it spoofed identity, shadowed the import path, linked to a 404 repo, and came from the same account as pybotnet.
