🆕 Brave researchers have uncovered vulnerabilities in zkLogin, a widely-deployed authorization system for blockchain transactions.
Our findings demonstrate the wider challenges facing zero-knowledge proof systems.
Like other zero-knowledge proof systems, zkLogin can verify that you’re a valid user without learning your identity.
However, zkLogin makes several assumptions during this authorization process that leave it open to attackers.
Today's blog explains the vulnerabilities we uncovered and the lessons they offer for anyone designing privacy-preserving authorization systems: brave.com/blog/zklogin/
Limiting Clawdbot's access will also limit risk. For starters, don’t use Clawdbot on your primary laptop with all your data and passwords. Instead, run it on a separate device like an old desktop or a VPS.
2) Use dedicated accounts
Give Clawdbot access only to burner emails, temporary phone numbers, etc. This ensures that your main accounts aren’t compromised.
AI agents that can browse the Web and perform tasks on your behalf have incredible potential but also introduce new security risks.
We recently found, and disclosed, a concerning flaw in Perplexity's Comet browser that put users' accounts and other sensitive info in danger.
This security flaw stems from how Comet summarizes websites for users.
When processing a site's content, Comet can't tell content on the website apart from legitimate instructions by the user. This means that the browser will follow commands hidden on the site by an attacker.
These malicious instructions could be white text on a white background or HTML comments. Or they could be a social media post.
If Comet sees the commands while summarizing, it will follow them even if they could hurt the user. This is an example of an indirect prompt injection.