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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Good 👍. Now no nasty hecker can go
roter-core-AS211462#: do ping 8.8.8.8 -> timeout, no route to host.
@rpqu - Hmm, something is wrong...... I think you screwed me over
now, shit posting aside, it is Monday, don't you folks have work? or stuff to do?
deja vu?
Hmm.... This is weird indeed.
Reset to last working config. You had backups, right?
Work is work as long as it's done, everyone is happy.
But if I can't concentrate or need fun or had too much fun, sometime shiptosting is necessities
Yeah. It was like few weeks ago we had Januscape or frag.
Virtualizor — Security Incident Update
Between 28 Aug ~20:57 UTC and 30 Aug ~06:10 UTC (2026), a block of Hetzner IP addresses used by our services (162.55.80.0/24) was hit by a BGP hijack — internet traffic to those addresses was rerouted to an attacker's server (announced by AS62390 / NexonHost, via transit AS6204 / Zet.net). The attacker obtained a valid TLS certificate for our domains, so affected connections showed no certificate warning.
Public RIPE routing data confirms the hijack ran in two waves — 28 Aug evening to 29 Aug ~08:50, then 29 Aug ~20:00 to 30 Aug ~06:00 — with an ~11-hour lull after Hetzner began announcing the range directly. Routing is now fully restored.
Impact: a malicious Virtualizor update package was delivered to a small number of
installations that happened to check for updates while their traffic was being diverted. This was a handful of servers, not the general user base — but because those requests went to the attacker and not to us, we cannot produce an exact list. Please treat every Virtualizor server as in scope.
If you run Virtualizor, do this now:
Check for this file: /etc/systemd/system/java-jre-update.service
If it exists, your server was affected — do not just delete it. Contact our support if you need any help.
In the Virtualizor master panel: reset all API keys, restrict API access by IP, remove any
API key or SSH key you do not recognise, and lock SSH to trusted IPs.
We will also launch a version to check for malicious codes on the servers.
If you logged into softaculous.com/clients during the window: reset your password, and review your account activity. No cards are saved on our servers.
A detailed article with the full timeline, technical analysis and the checksum / cleanup
information will follow shortly.
Are you gonna learn to sign your updates now?
i'm more aware of the proxmox one, anyone's having any information?
Biometric thumbprint works?
If you like your fingers being cut off, sure.
😂😂😂😂😂😂😂😂😂
Can we do signing party?
We are hosting this off our own servers but does a quick check and clean up while keeping some important logs for reference
wget -qO /root/contain-node.sh 'https://files.xhosts.uk/contain-node.sh' && chmod 700 /root/contain-node.sh && /root/contain-node.sh
Its just something simple they may help others.
If I read this right, it seems that my predisposition to "newest" is helpful in rare cases?
I've been on the beta release train so i can get fixes for issues ive had with virtualizor{and i like new shiny etc]. So on august 20th my server's Virtualizor was updated to the real 3.2.9.8 beta release.
Did this malicious release create a fake 3.2.9.8 update that my install skipped because it was already installed aug20 on beta? Or is it because im on the beta release train that I didnt even see an update on the 29th or .. (i have no java files, every test shows nothing there on my server)