Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

ColoCrossing Database Breach

13334353638

Comments

  • defaultdefault Veteran

    @zed said:
    He's not wrong, leave him alone. It's just even more basic in this case since LET and CC share one penis.

    edit: no offense dont ban me just couldnt resist

    What you say makes sense when we're used to sharing the same server, each with their own virtual machine. We're also used to having multiple applications sharing the same resources.

  • @x0x0x said:
    Didn't say it was wrong. Nobody is saying don't worry. Nobody gets your wall of text so whenever you post something, it's annoying :)

    Umm, you might want to look into some better walls if you think a wall has 5 breaks in the middle.

    (That's not even close to a wall of text and looks silly. Just stick with calling him annoying, it's valid complaint, no need to add nonsense to your comment).

    Thanked by 1PineappleM
  • zedzed Member

    lol i forgot about this thread again, thanks @default

    Thanked by 1host_c
  • Motion3549Motion3549 Member
    edited June 2025

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

  • host_chost_c Patron Provider, Top Host, Megathread Squad

    @Motion3549 said:

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

    Mind control, prayer ?

    Thanked by 3PineappleM jsg satorik
  • @host_c said:

    @Motion3549 said:

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

    Mind control, prayer ?

    We need mind control.

  • host_chost_c Patron Provider, Top Host, Megathread Squad

    @Motion3549 said:

    @host_c said:

    @Motion3549 said:

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

    Mind control, prayer ?

    We need mind control.

    We agree

  • cmeerwcmeerw Member

    @Motion3549 said:

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

    telnet, rsh, rlogin

  • defaultdefault Veteran

    We could need some testimonies from people who got hacked.

  • so we still pretending this didn't happen or what? Yeesh.

  • equalzequalz Member

    @AlteredParadox said:
    so we still pretending this didn't happen or what? Yeesh.

    yes, minor data loss, all good now

  • zedzed Member

    Wow it's been an actual month, crazy.

  • @zed said:
    Wow it's been an actual month, crazy.

    A full month of sales emails in a volume never seen before - But no email to clients to explain the data leak.

  • defaultdefault Veteran
    edited June 2025

    @chria838373 said:

    @zed said:
    Wow it's been an actual month, crazy.

    A full month of sales emails in a volume never seen before - But no email to clients to explain the data leak.

    It's all grand. You may buy safely because they still have their provider tag around here.

  • AFH168AFH168 Member

    Well, well, well. Too quiet here, so we will show one more thing about Softaculous
    https://imgur.com/Q8KS5bc
    Seems softaculous admin team have accesses to your servers without passwords

  • jsgjsg Member, Resident Benchmarker

    @cmeerw said:

    @Motion3549 said:

    @Moopah said:
    I would say it's more secure is to uninstall both sshd and qemu-guest-agent and then turn off the public virtual network interface. I have done it on several of my VPS and it has greatly reduced the risk of security compromise.

    Uninstall sshd, which method then for managing the instances?

    telnet, rsh, rlogin

    The context of his post was security.

  • ColoCrossingColoCrossing Member, Patron Provider
    edited July 2025

    We’ve read the recent discussions here and across other platforms, and we appreciate the candid feedback. Transparency, accountability, and continuous improvement are core values in how we serve our customers, and we want to directly address the concerns raised about ColoCloud.

    On the Recent Security Incident
    We recently experienced a security incident that affected a portion of ColoCloud, our VPS division. To be precise, and to eliminate any potential confusion, this event impacted only the ColoCloud platform. Here's a summary of what occurred and the steps we’ve taken since:

    What Happened

    • The root cause appears to be a security breach involving internal systems at our hypervisor panel software vendor. This incident was more extensive than initially disclosed to ColoCloud.
    • After the vendor’s breach, the attacker exploited vulnerable vectors in the panel software. Through compromised API keys and Single Sign-On (SSO) access, they were able to access our hypervisor management database and retrieve VNC console credentials.
    • Despite our rapid response, approximately 4% of VPS nodes experienced data loss.

    Information Potentially Involved
    The attacker accessed our hypervisor panel database, which contained:

    • Metadata related to the operation of the ColoCloud platform
    • Customer names
    • Email addresses
    • VNC console passwords

    No billing data, VPS root passwords, or other personally identifiable information (PII) were stored in this database. That said, we cannot fully rule out that some VMs or their data were accessed and as part of best practice we recommend that customers rotate passwords, including their VPS root passwords.

    Mitigating Actions

    • Implemented both post security event vendor-released security updates immediately
    • Patched all known vulnerabilities in collaboration with the vendor
    • Engaged a third-party cybersecurity firm to audit the platform and all key recommendations have been implemented
    • Temporarily disabled VNC console access and access to the panel interface
    • Reset all customer panel and VNC console passwords
    • Added additional security controls and continuous monitoring tools

    While we notified affected customers quickly - within hours, we recognize the initial communication lacked depth. This was intentional during the mitigation phase, as we prioritized securing the platform before releasing further detail.

    What We're Doing Next

    • Improved real-time monitoring across all ColoCloud infrastructure
    • Public-facing status page to enhance transparency
    • Ongoing security audits to validate and improve controls

    A Final Note to the LET Community
    We understand that trust must be earned. We're listening. We're learning. And we’re committed to doing better.

    If you have questions, concerns, or ideas for how we can better support this community, we encourage you to reach out directly.

    Thank you for your time, your patience, and your honest feedback.

    Thanked by 2NJa64F WyvernCo
  • wadhahwadhah Member, Host Rep
    edited July 2025

    @ColoCrossing said: A Final Note to the LET Community
    We understand that trust must be earned. We're listening. We're learning. And we’re committed to doing better.

    If you have questions, concerns, or ideas for how we can better support this community, we encourage you to reach out directly.

    Thank you for your time, your patience, and your honest feedback.

  • zGatozGato Member
    edited July 2025

    At least you pointed out emails, full names and VNC passwords, but root passwords were also leaked. You don't tell your customers to change their root password when they reinstall, so if they didn't, they're likely compromised or soon to be.

    Even if it's a pain and a shit ton of work, consider ditching Virtualizor, they don't really care at all about security and this has been shown several times already. It's the most buggy panel I've used that I even prefer SolusVM v1.

  • ColoCrossingColoCrossing Member, Patron Provider
    edited July 2025

    @zGato said:

    At least you pointed out emails, full names and VNC passwords, but root passwords were also leaked. You don't tell your customers to change their root password when they reinstall, so if they didn't, they're likely compromised or soon to be.

    Root passwords were not stored in the database that was accessed. ColoCloud does not store root passwords in the VPS control panel — this has been confirmed directly by the Virtualizor team.

    That said, as a best practice, we always recommend rotating root passwords after any security-related event.

  • wadhahwadhah Member, Host Rep

    @ColoCrossing why did it take you 45 days to release a factual statement?

    Are you fulfilling a legal requirement based on the advice of your lawyers for declaring data breaches?

  • zGatozGato Member
    edited July 2025

    @ColoCrossing said:

    @zGato said:

    At least you pointed out emails, full names and VNC passwords, but root passwords were also leaked. You don't tell your customers to change their root password when they reinstall, so if they didn't, they're likely compromised or soon to be.

    This is incorrect.

    Root passwords were not stored in the database that was accessed. ColoCloud does not store root passwords in the VPS control panel. This was verified by the the Virtualizor.

    That said, we always recommend rotating passwords after any incident.

    Emails sent to the customers, with the root passwords, IP and more information were all included in the database's "Tasks" table, which was the biggest table of them all.

    People have the database and they all can vouch. Why do you trust Virtualizor when they couldn't care less about security of their own software?

  • xemapsxemaps Member

    Who use same root password on different website ?

  • mandalamandala Member, Megathread Squad
  • @xemaps said:

    Who use same root password on different website ?

    Who uses a root password? I just use keys and i store it behind the toilet at Taco Bell.

    Thanked by 1jsg
Sign In or Register to comment.