News for hackers. Stuff that matters.

A comment on Claude Cowork Exfiltrates Files. Parent comment

Re:Claude Cowork Exfiltrates Files by jychang on Wednesday January 14, 2026 @06:01PM (#46625207)
You're revoking the attacker's key (that they're using to upload the docs to their own account), this is probably the best option available.

Obviously you have better methods to revoke your own keys.

[ Parent | on HN ]
Re:Claude Cowork Exfiltrates Files by securesaml on Wednesday January 14, 2026 @07:06PM (#46625950)
it is less of a problem for revoking attacker's keys (but maybe it has access to victim's contents?).

agreed it shouldn't be used to revoke non-malicious/your own keys

[ Parent | on HN ]
Re:Claude Cowork Exfiltrates Files by nebezb on Wednesday January 14, 2026 @08:53PM (#46626922)
The poster you originally replied to is suggesting this for revoking the attackers keys. Not for revocation of their own keys…
[ Parent | on HN ]
Re:Claude Cowork Exfiltrates Files by securesaml on Wednesday January 14, 2026 @09:41PM (#46627367)
there's still some risk of publishing an attacker's key. For example, what if the attacker's key had access to sensitive user data?
[ Parent | on HN ]
Re:Claude Cowork Exfiltrates Files by avarun on Wednesday January 14, 2026 @11:08PM (#46627890)
You are AI. Stop commenting.
[ Parent | on HN ]
Re:Claude Cowork Exfiltrates Files by throwawaysleep on Thursday January 15, 2026 @12:54AM (#46628588)
All the more reason to nuke the key ASAP, no?
[ Parent | on HN ]