Bunny.net disclosed a security incident involving a third-party infrastructure provider that reported unauthorized access to its server-management software. One Bunny.net CDN node in Armenia was hosted on the provider’s equipment. Within 20 minutes of being notified, Bunny.net stopped routing traffic through the node, preserved security logs, wiped the server, and revoked its access to other systems; the server has since been permanently removed. Bunny.net and the provider found no evidence that the node or its data was accessed, though the investigation has not ruled out that possibility.
If access did occur, information potentially exposed on the node included temporarily cached CDN content, Pull Zone configurations, and TLS certificates stored there. Bunny.net says account data and other customer data were not on the server, and no internal systems were affected. As a precaution, it revoked and replaced certificates for its platform domains. Managed certificates for custom domains are being reissued gradually with new private keys, a process now expected to finish by the end of October 31; existing certificates remain in use until replacement, so customers using managed certificates need take no action. Customers who manage their own certificates are advised to revoke and reissue them using new private keys. Bunny.net is monitoring the situation and will provide further updates if investigations uncover findings relevant to customers.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.