#nasa #artemis #outlook #microsoft #microslop
| https://twitter.com/nunohaien | |
| GitHub | https://github.com/tillmannw |
| https://twitter.com/nunohaien | |
| GitHub | https://github.com/tillmannw |
Two scenarios possibly resulting from today's Claude Code source code leak¹:
1. Attackers study the built-in permission system to figure out how to bypass it. Claude Code is the target here. It is strange that the software requesting permission is the same that enforces security boundaries, anyway.
2. Attackers distribute custom builds that
do nasty stuff like stealing API keys, running commands, backdooring code. Here, a specially crafted Claude Code is the attack vector.
We are aware of recent reports regarding targeted phishing attacks that have resulted in account takeovers of some Signal users, including government officials and journalists. We take this very seriously.
To be clear: Signal’s encryption and infrastructure have not been compromised and remain robust. These attacks were executed via sophisticated phishing campaigns, designed to trick users into sharing information – SMS codes and/or Signal PIN – to gain access to users’ accounts.
Ach wie cool, unsere Kamera auf dem Sportplatz Kleinenbroich hat den Meteoriten eingefangen:
@G33KatWork Cool to see this published, and pop up on my feed! I actually consulted with the writers of that video on the tech details of the backdoor.
If you’d like a much less polished (but more technical) explanation, I gave a lecture about a month after it happened: https://youtu.be/Q6ovtLdSbEA
