>>105581037 (OP) >Yesterday, a threat actor claimed to have breached cock[.]li using the latest RCE vulnerability affecting RoundCube (which cock[.]li uses).
>The leak appears to be authentic, containing data on approximately 1,023,800 users (dating from 2016 to 2025) and around 93,000 contacts.
>The compromised data does not include passwords or plaintext emails, but it does contain names, email addresses, and login attempt timestamps. https://x.com/ReyXBF/status/1933555211185819835
>>105583562 >The new certificate was issued on April 16 >The warrent canary hasn't been updated since April 21 https://cock.li/canary.asc.txt
Vincent isn't here anymore, and the glowies couldn't be bothered to update the roundcube install
>>105583595 >Until further notice, THIS CANARY SHOULD BE UPDATED EVERY 72 HOURS. Under no >circumstances should we let this canary go 96 hours without an update unless a >PGP-signed message changes the schedule.
oh nyo
>>105585232 >The bug stems from unsanitized $_GET['_from'] input, enabling PHP object deserialization and session corruption when session keys begin with an exclamation mark. >The flaw, which impacts Roundcube versions 1.1.0 through 1.6.10, spanning over a decade >Shortly after the patch was released, hackers reverse-engineered it to develop a working exploit, which they sold on underground forums. https://www.bleepingcomputer.com/news/security/over-84-000-roundcube-instances-vulnerable-to-actively-exploited-flaw/
>>105583016
How exactly do you expect someone to send you over $100k on a pinky promise you'll hand over a bunch of mostly useless metadata? Do these guys use escrow or something?
>>105581037 (OP)
Why are you using this service without configuring a male client to fetch and send the emails? Are you people really using the web browser interface? It still works for me.
