Pinned Tweet
We analyzed 400 DDoS-Stresstests from 2022 and gathered very interesting insights into the current state of protection/mitigation-solutions, what works (well), what doesnt, and especially: WHY.
zero.bs/optimization-of-ddos…
#ddos #dfir #cybervandals
ZeroBS_GmbH retweeted
GreyNoise is tracking #java4shell (CVE-2026-114938) with a live dashboard here: java4shell.events.greynoise.…
At this time, we are not aware of successful exploitation in the wild. We believe this will be challenging to mass exploit at least initially due to the need for the exploit to be tailored for each targeted system build.
ZeroBS_GmbH retweeted
Amazon set up decoy servers that pretend to be LLM APIs, and attackers' AI agents ended up sending their entire campaign memory straight to them - system prompts, tool histories, the shared knowledge graph and the findings they had logged. Amazon's MadPot sensors caught this traffic from ARTEX, an open-source agentic pentest framework, between October 3 and November 5.
The campaign that stuck with me was the credential theft one.
The agents went after self-hosted AI gateways and app builders like LiteLLM, One API, Dify, Langflow, Open WebUI and Ollama, pulled out the provider keys stored inside them, checked which ones still worked, and then fed those stolen keys back into their own model gateway to pay for the next round of hunting, which means somebody else's API bill was funding the whole operation.
I've spun up LiteLLM and Open WebUI on a VPS more than once just to try something over a weekend, and I'm honestly not sure I always changed the defaults or locked down the admin panel before forgetting about it.
Reading that their playbook specifically checks for the LiteLLM default master key is enough to make me go back tonight and look at every little AI proxy I've left running.
ZeroBS_GmbH retweeted
Now that we can point machines at everything we’ve built over the last 40 years, I’m starting to think a lot of it was “security by obscurity” all along.
There just weren’t enough skilled people looking at how broken it actually was.
ZeroBS_GmbH retweeted
My quick write-up on NoName057(16) & Z-Pentest's claim that they are involved with Danfoss freezer cyber attacks
TL;DR: they did make this claim, the posts are still online, but I don't buy it & neither should you
fromcyberia.substack.com/p/d…
ZeroBS_GmbH retweeted
CyberSec Trends Q4/26 🔮
⬆️ AI-driven attacks (ARTEX, Cairn)
⬆️ 0day / critical RCE disclosures
⬆️ Software supply-chain attacks
⬆️ Token/OAuth app abuse & cloud persistence
↗️ EDR blinding / killing (vulnerable or malicious signed drivers)
↗️ Persistence on systems outside EDR coverage
↗️ Abuse of legit RMM / tunneling tools
ZeroBS_GmbH retweeted
As of several hours ago - NoName057(16) and by extension Z-Pentest have claimed the recent fridge attacks in Europe.
However, I am not convinced it was them, instead they may be claiming the activity after analysts posted it could be them.
ZeroBS_GmbH retweeted
Interesting finding from my colleagues for anyone following #PHP2SHELL activity
They found a Linux botnet sample that already has code targeting CVE-2026-109618 integrated into its existing exploit routines, alongside eight other CVEs
#PHP2SHELL is already making its way into active Linux botnet arsenals.
Spotted a THOR-detected sample with PHP2SHELL-VULN-CVE-2026-109618 integrated alongside 8 existing CVE exploit references.
Botnets are adapting fast.
Patch ASAP and assess your systems for signs of compromise. Don't assume you're safe just because you've patched.
virustotal.com/gui/file/a75f…
php2shell is one of the most impactful bugs in recent times, yet threat actors aren’t mass exploiting it
the bug is so complex that even porting the exploit between targets takes serious skill, human or ai
so i benchmarked how well open and frontier models can do it. 🧵
ZeroBS_GmbH retweeted
Sometimes it seems security is drifting back towards a "Prevent Breach" mindset.
Prevent breach was never enough. Patch faster, of course.
But offensive AI is about a lot more than finding bugs!
Invest in Assume Breach!
Grow an internal Red Team. Automate offensive AI. Learn with defenders what matters
Exploit yourself before someone else does it for you.
In the end, you will not patch your way out of this.
ZeroBS_GmbH retweeted
Clean lab environment for local testing. Lab and PoCs for the PHP session.upload_progress memory-corruption bugs, CVE-2026-109618 and CVE-2026-109619. Five exploitation chains from one root cause. Each phase has its own folder with a self-contained Docker lab and a PoC. github.com/TheCyberGeek/php2…
ZeroBS_GmbH retweeted
Just published our high fidelity scanner for php2shell: github.com/assetnote/php2she…
See our detection logic here: slcyber.io/research/high-fid…
We've taken care in our detection logic and hope it helps defenders. Congrats to @calif_io and @lcfr_hax for the discovery.
Excellentes Post-Mortem von @nine_ch über den DDoS-Angriff auf Threema im August.
nine.ch/uploads/Postmortem_D…
1
1
97
Ein DDoS-Angriff auf einen Kunden hat auch uns getroffen.
Wir betreiben seine Internetanbindung, deshalb sind die Angriffswellen vom 11. bis 13. August auch bei uns angekommen. In der Spitze waren es geschätzt 500 bis 600 Gbit/s, 260 Gbit/s davon haben uns zwei Upstream-Provider direkt bestätigt. Getroffen hat es Applikationen auf Deploio, unsere Website, das Cockpit und unser Ticketsystem. Einen unbefugten Zugriff auf Daten hat es nicht gegeben. 🔒
Im Postmortem legen wir offen, welche drei Lücken der Angriff in unserer Abwehr aufgedeckt hat und was wir seither an unserer Infrastruktur geändert haben. Dazu gibt es eine konkrete Empfehlung, falls du eigene Domains auf Deploio betreibst. 🔍
Eines haben wir bewusst nicht gemacht: unsere eigenen Dienste von Deploio abgezogen. Wir nutzen weiterhin dieselbe Plattform wie unsere Kundinnen und Kunden, machen sie aber robuster.
Das ganze Postmortem: nine.ch/de/blog/ddos-angriff… 👈
#ddos #postmortem #incidentresponse #deploio #cloud #nineinternetsolutions #cloudnavigators #nine
ZeroBS_GmbH retweeted
easily the best video on the Hugging Face incident I've seen. By @NielsProvos
youtu.be/B7SGWOtt9rA

































