Keybase account hacked - no response from notify@keybase.io or privacy@keybase.io

Reporting this issue here since there has been no response from Keybase.

On Tue, Sep 24, 2019 at 6:16 PM Keybase wrote:
You just changed an email address from [redacted] to subashik@yandex.ru. Since you changed your primary email address, Keybase will send important emails to your new primary email, subashik@yandex.ru.

On Tue, Sep 24, 2019 at 9:51 PM [redacted] wrote:
Dear Keybase staff,
Thank you for this notification. I believe my account has been hacked as I did not authorize this change. I have no idea who owns subashik@yandex.ru - that is not my email address. Please disable access to my keybase.io account. My email address continues to be [redacted] and this is the account to which you can send information to reactivate my account/change the password/set up two-factor authentication, if available. Thank you.
Sincerely,
[redacted]

[redacted] | Sep 24, 2019, 10:55 PM (11 hours ago)
[redacted]
to Keybase, privacy | to Keybase, privacy
to Keybase, privacy

I've reviewed the chain for my Keybase account peterthegreen and the final chainlink which I authorized was Chainlink #4 on 12/16/17 at 2:20pm. I have not authorized any activity since then. Some unknown person has hacked my Keybase account. Please disable access to this account ASAP and let me know how I can recover the account.
Thank you.

This report names no files, tests, or implementation entry points. It describes an unauthorized Keybase email change and requests account disabling and recovery, so it is a security and account-support case rather than a scoped contribution. No newcomer-ready change or verifiable implementation outcome is identified.

Written by the indexing model from the issue text.