Thank you for the clarification; the situation is now clearer. That said, my original concern remains: this matter should have been handled privately. Publicly announcing the discovery of a vulnerability in a well-known Hive "platform" can inadvertently draw attention to the broader Hive ecosystem and increase risk.
One could also argue that heightened focus on Hive-related platforms may encourage additional vulnerability research by malicious actors. While bridge infrastructure is generally understood to be a common attack surface, the recent Hive Engine bridge incident underscores the importance of responsible disclosure. It also raises the broader question of how many other undiscovered vulnerabilities may still exist across the Hive ecosystem...