Thread

Replies (41)

More people should get hacked. This is fantastic stuff. As @david pointed out here, be sure to report the old account to help knock it out of the GrapeRank WoT!
david's avatar david
Given Brainstorm as it is currently implemented, if a handful of people use NIP-56 to report this nsec, it will only take a small handful of reports to knock the GrapeRank score down to zero, which will prevent this profile from showing up on profile keyword searches in the future, once we have a few search engines using the GrapeRank metric to filter results. Unfollowing helps too but as a general rule, you’re never going to get enough people to unfollow a compromised nsec. Muting will also reduce the 🍇-Rank score but not as much as reporting. NIP-56 does not specify a reportType for “compromised” — maybe we should update the nip? For now, reportType “other” would work best; or just put “compromised” as the reportType even if it’s nonstandard. https://nostr-nips.com/nip-56
View quoted note →
↩ replying to npub1rr7v...wudh
Adam Soltys's avatar Adam Soltys
With the Coinos account I straight up uploaded the nsec to GitHub by accident. With this personal one I'm pretty sure it's because I had it loaded into a Coinos account with a weak password on it that an attacker was able to brute force to decrypt it. We don't store encrypted nsecs anymore since adding support for remote signers so no one else should have this issue, it was just in one of my old accounts.
View quoted note →