https://images.hive.blog/DQmRFd6EYLGNYnPG5o945tZpPz5VN8nhPQsiho6ZWm4zrVG/image.png @guiltyparties and @hivewatchers (ie. @spaminator @steemcleaners) marked 3speak.co as a phishing website in one of the APIs that @keys-defender consumes. This was done in order to safeguard users because the .co domain was compromised. - @3speak’s announcement: https://hive.blog/hive-181335/@threespeak/announcement-3speakco-is-currently-down-switched-to-3speaktv This temporary blacklist will remain in place until the issue is resolved. Please hang in there. The downvotes were automated and we’ll try to remove them afterwards. ----- UPDATE: New posts using the old domain will now not be **downvoted**. ----- Clarifications from GP:
![C1C88BB6-DEF1-4FC0-8E6F-7B67FF719F4E.jpeg](https://images.hive.blog/DQmb9W8csehRugt6YTTASd2fTX258JkxtE6XD1Ajap3kmYE/C1C88BB6-DEF1-4FC0-8E6F-7B67FF719F4E.jpeg) ![image.png](https://images.hive.blog/DQmc1zu4JsN14yDqJ7rhqfcnpKVZy4oMTgEshBdufpbzZYR/image.png) -----

Update/clarification:

Got my 4-day old baby crying in my arms all day so I could not be on top of this.

Recently I gave partial control of my bot to @spaminator @hivewatchers @steemcleaners and they added the 3speak.co link to their blacklist that my bot uses. - If you're marked as a phished account you'll get the auto-replies that warn other users ( [example](https://hive.blog/hivedev/@keys-defender/antiphish-keys-defender-bot-1615158701499) ) - If your post or the metadata of your post still uses the 3speak.co domain you'll get the auto-reply that warns other users about the compromised domain ( [example](https://hive.blog/hive-175836/@keys-defender/antiphish-keys-defender-bot-1615157380553) ) Please reach out to the admins of their discord server so that they can decide whether to remove you from @spaminator's list of phished accounts:

https://discord.gg/dfUGwbBy

----- Update: - 3speak.co is still blacklisted: https://spaminator.me/api/p/domains.json - The users that complaining about the warnings are indeed in the list of hacked accounts: https://spaminator.me/api/bl/hacked.json - Old posts edited by users to use 3speak.tv still get the warning because the metadata still uses 3speak.co and that triggers the bot (as expected). Changes that I just released: - From now on the bot will check if the phished account message contains a link before replying (still risky because the attacker could just post a link like "new airdrop, visit: t.ly/air9" and users could copy and paste it) - Added workaround for metadata issue Take care, kd ——- Update - from hivewatchers discord: ![FB599A90-3F89-4060-9B3C-1CD8CA49292C.jpeg](https://images.hive.blog/DQmQWzybvbfN7wRWPrZbZVkyNt2rJtsREMXZMajN4Fd4tb6/FB599A90-3F89-4060-9B3C-1CD8CA49292C.jpeg) ----- Final update: the issue seems now resolved and the domain has been restored -> https://peakd.com/threespeak/@threespeak/important-announcement-we-have-control-of-all-top-level-domains-including-3speakco

RE: El valor de un buen comentario.