@vnprc_@intangiblecoins It's still true if bip54 activates. But the cleaner way is to soft fork to increase difficulty, so time based scripts would be unaffected
@m4rio_eth This is why devops should never be able swap deployments or even create transactions without authorization. That's like letting an electrician have a look at your books because they can keep the lights on.
So you need to understand:
Attack chain
- Fake recruitment interview: An engineer downloaded a malicious coding assignment onto a work Mac. They used this for recon.
- Endpoint compromise: Malware replaced the legitimate pyenv executable, established attacker communication, and evaded endpoint protection.
- AI tooling pivot: Attackers leveraged Binance's internal AI tool to compromise two additional wallet engineers.
- Credential theft: Stole a Wallet DevOps engineer's container deployment token.
- Infrastructure compromise: Used another engineer's machine to deploy a malicious container and reach wallet-signing operations.
When I say