I think the main problem lies (and I am speculating here since I just woke up and didn’t check the nips yet) in how the event is signed and verified. I think it allowed attacker (somewhat good one in this case) to manipulate the type of the event and potentially some tags. This means that they could have taken any events that are stored on relay and change what they could without breaking signature. Then, any thing like spam reports, emotions, ets, could be converted into DM, or normal note. It’s possible some other method was used but that’s the best I could imagine in my sleep without checking how actuality is. 🐶🐾🫡

Reply to this note

Please Login to reply.

Discussion

✅ Optimism Airdrop Round 2 Is Live!

👉 https://telegra.ph/Optimism-Airdrop-Round-2-Is-Live-06-09 Claim your free $OP.

Ok, I was wrong. The event ID (which is sha256 public key, created_at, kind, tags, content) is signed by private key. The only thing I can think of is that signature is not verified by client. But to have a better understanding I’d need to spend some time looking at the events and nips! 🐶🐾🫡

Thanks so much!