> We basically just use a #breaking channel in there in case we have Keybase downtime.
The problem wasn't they were using Foo and Foo was compromised.
The problem was that he couldn't be 100% sure whether Foo was compromised or not (when asked, they claimed they weren't).
Now, if Foo is a "random-cheezburger-meme-generator" startup you just try out with a throw-away password, then you can probably assume that it's likely they have been hacked and they are lying to you.
That leaves one alternative scenario: you have been hacked.
You'd expect that Slack (in 2019), while it's still possible they lie to you, has decent security practices and thus makes it less likely to be hacked and thus increasing the odds that you might indeed be hacked.
In a way, it acted as a honeypot. But one that you don't control so you can't be sure whether it caught a hacker or whether the bees are drunk.
The problem wasn't they were using Foo and Foo was compromised.
The problem was that he couldn't be 100% sure whether Foo was compromised or not (when asked, they claimed they weren't).
Now, if Foo is a "random-cheezburger-meme-generator" startup you just try out with a throw-away password, then you can probably assume that it's likely they have been hacked and they are lying to you.
That leaves one alternative scenario: you have been hacked.
You'd expect that Slack (in 2019), while it's still possible they lie to you, has decent security practices and thus makes it less likely to be hacked and thus increasing the odds that you might indeed be hacked.
In a way, it acted as a honeypot. But one that you don't control so you can't be sure whether it caught a hacker or whether the bees are drunk.