I imagine you just installed Connect? If you were already logged in then it won't fix the problem. The issue is that all login tokens have expired since the attack.
To add to this, I dug up old stuff and it turns out this was probably because the same person who came up with the name had a few hours prior suggested we use this great bee art for the server icon!
(This is my non-artist opinion - I don't know shit) The style and detail has improved a lot but I feel like the biggest improvement is that the self-portrait is more dynamic compared the old one - I think it gives it more life.
It's possible that there are breaks in federation. It could be because of one main reason : Beehaw didn't send it to mastodon. Now why would that happen?
It could be that Mastodon blocked it for whatever reason
It could be that the server crashed and so all federation outwards was lost
Note that if this were a Lemmy feature, if we had been infected, an admin could've gotten hacked and as a result, disabled that feature. I'm not really sure what can be done to make Beehaw foolproof. That said, the UI has since been hardened by CSP headers so this type of attack should no longer be possible.
If you try the same on the website, does it work? Had you tried setting up 2FA at some point?