pull down to refresh
0 sats \ 4 replies \ @cryptocoin OP 3 Aug 2022 \ on: 🧵 Widespread malware attack on GitHub bitcoin
Hard to conclude that this is directly related to the solana private key leaks. Nevertheless, you should rotate your application secrets if you used any of the fake libraries on GitHub.Always use rotating secrets if you can and vet the libraries you use.
reply
I have yet to find a single real GH org; it's all copies with 0 stars, created in the last 6-10 days.
As this is making the rounds, some more context:This appears to be an extremely broad, low value, low effort, and likely low impact attack.Given two major *coin attacks in the last 24 hours or so, infosec news gets more attention than usual.
reply
If you use npm, go get or other automatic dependency grabbing systems you better be pinning deps to particular hashes.Do not blindly trust deps by name.Do not allow deps to automatically upgrade to a newer version.Hard part: Your deps might be blindly trusting their deps.
reply
UPDATE
GitHub is investigating the Tweet published Wed, Aug. 3, 2022:
- No repositories were compromised
- Malicious code was posted to cloned repositories, not the repositories themselves
- The clones were quarantined and there was no evident compromise of GitHub or maintainer accounts
reply