Re:AWS merges malicious PR into Amazon Q
by rusteh1 on Wednesday July 23, 2025 @07:23PM
(#44665111)
I'm not a git expert, but how was the attacker able to push the stability branch directly to the Amazon owned repo? The PR would have been to merge the modified branch to main right?
[ Parent
| on HN ]
Re:AWS merges malicious PR into Amazon Q
by shdjhdfh on Wednesday July 23, 2025 @07:32PM
(#44665194)
My guess is that skywhopper is correct. We're only able to see the tail end of the attack, but the repo was likely compromised in some way.
Re:AWS merges malicious PR into Amazon Q
by wunderwuzzi23 on Thursday July 24, 2025 @09:26AM
(#44670422)
AWS issued a post and they talk about revoking and replacing a credential.
So maybe the hacker was able to directly push?
https://aws.amazon.com/security/security-bulletins/AWS-2025-...
Joseph's 404 article quotes the hacker as saying they "got admin privileges on a silver platter," so I think this is it: first part of the breach was gaining the GitHub permission to create a branch. Possibly just by asking.