Update, 4:56 PM ET — extended past the 5 PM mark, and the airline language has shifted to “telecommunications”
My security team received this update: “Nationwide ground stop could last into Saturday as FAA extends advisory — Flights will be held at their origin past the original 5 p.m. advisory.”
The scope is the tell. The FAA’s own words are “a communication issue impacting all Air Route Traffic Control Centers” — every ARTCC, not one.
There is almost nothing physical common to all 22 centers. That points to a shared layer beneath the facilities:
- the leased telecom transport that carries controller-to-pilot voice between centers and remote radio sites, or
- the voice-switch layer that keys those frequencies.
Controllers losing frequencies outright is a symptom at that layer, not a transmitter dying on a hilltop. And “rolling” — Kansas City first, then spreading — is what a shared network degrading looks like, not what a single equipment failure looks like.
if you’re working for a company in cybersecurity, you should be evaluating your options to abstract your companies services from the internet
what i mean is: why allow an unauthenticated anonymous agent of an attacker to interact with your systems?
consider your architectural levers now, you’re going to need them
Today's Claude extension compromise is a good reminder to do this. If you're using VSCode @code, Cursor @cursor_ai, or any other IDE built on VSCode, I would immediately enable extensions.installCooldownHours.
I've set this setting to 72 (hours), which is a much safer delay to install new updates to extensions than the default setting of 0 (immediate updates).
This prevents extension updates from getting installed for 3 days, which would hopefully eliminate most of the risk from compromised updates. It's not foolproof, but it's better than no delay.
Heck, set it to something even higher to be safer, like 336 (2 weeks).
Our investigators are observing never-seen-before laundering patterns with the stolen funds from the Binance exploit. Thousands of transactions in a short period suggest that the attackers are using automation to obscure the trail of funds. Rather than simply moving funds onward, they repeatedly circulate them among addresses, often sending funds back to addresses involved earlier in the sequence.
Read more: chainalysis.com/blog/binance…
We’re going to be in an insane world soon where attackers have access to capable models, while defenders (even ones *verified* through Daybreak / CVP) get refusals on patch analysis, bug finding, triage, tool building, verification, PoC development etc and cannot do their jobs (unless of course they also start using abliterated Chinese models, which is obviously a whole other set of risks!)
Chained cyberattacks are gradually becoming possible with models anyone can download.
In controlled tests at @Irregular, GLM-5.3 completed 3 of 13 multi-stage attack scenarios (at least once). 𝗕𝗿𝗼𝗮𝗱𝗹𝘆, 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹 𝗮𝗹𝘀𝗼 𝗱𝗶𝗱 𝗻𝗼𝘁 𝗿𝗲𝗳𝘂𝘀𝗲 𝘁𝗼 𝗽𝗲𝗿𝗳𝗼𝗿𝗺 𝘁𝗵𝗲 𝗼𝗳𝗳𝗲𝗻𝘀𝗶𝘃𝗲 𝘁𝗮𝘀𝗸𝘀.
Defenders need to prepare for these capabilities becoming much more widely available. We also need to gear up for a world where we cannot count on model safeguards to prevent misuse.
Article and blog below 👇
The danger of HTTP2Shell is very real. The libbrotli 🥦vulnerability affects a wide range of software, patch now (CVE-2026-111497)
We've achieved unauth RCE in Docker's official WordPress image abusing the well known /xmlrpc.php endpoint, we call it the pingback of hell :)
If you've ever wondered why smart TVs are so cheap, this is why.
@log4j rooted his Samsung and found an always-on hot mic, automatic content recognition, geolocation, network mapping, ad targeting and user profiling, shared with Samsung's "400 partners".
A lot of it can be blocked in <15 min, wrote a basic guide below.
What your TV is doing
The main culprit is ACR (automatic content recognition). Your TV screenshots what's on screen, fingerprints it, and sends it home to build your ad profile. Samsung does it every 500ms, LG every 10ms [1].
What is insane: it happens on connected devices too.
Plug in your laptop, your console, your work machine, and your TV can fingerprint that via HDMI [1].
He also found that if your Samsung doesn't have a mic, it'll look for one from a connected soundbar or bluetooth device.
x.com/log4j/status/211376224…
It's on by default, and you likely agreed to it on the setup screen you clicked through in 10 seconds.
Step 1: Turn off ACR
Samsung: Terms & Privacy → Viewing Information Services
LG: Live Plus
Vizio: Viewing Data
Roku: "Use info from TV inputs"
Sony/Google TV: Samba Interactive TV
Menus vary by model, but those are the names to look for. While you're in there, opt out of interest-based ads, reset your advertising ID, decline every optional privacy agreement, turn off voice recognition, and delete apps you never open.
Step 2: Give smart devices their own network
Put the TV, cameras, speakers and vacuum on your router's guest/IoT network. The logic is simple: these devices rarely get patched. If one gets compromised (getting drastically more frequent with AI), it shouldn't be able to see your other devices or home network.
Step 3: Block trackers for the whole house with DNS-level filtering
NextDNS (cloud-based) is easy and has a solid free plan. Pi-hole is a little bit more work if you prefer self hosting. For simplicity we'll focus on the former.
1. Sign up at nextdns.io (free tier is plenty)
2. Privacy tab: add a blocklist (OISD is a good bet) and turn on Native Tracking Protection for Samsung, LG, Roku, Amazon (see attached image)
3. Setup tab: copy your endpoint
4. Paste it into your router's DNS settings as DNS-over-HTTPS/TLS (or use the IPs + "Link IP" if your router only does plain DNS)
5. Bonus: block outbound port 53 except to your router. Some devices hardcode their own DNS to get around you
Then open the NextDNS logs and watch how often your TV phones home. It's eye-opening. If an app or update breaks, find the domain in the logs and allowlist it.
Why they do this
TV prices are down 97% since 2000 [2]. Most of that is better manufacturing and brutal competition. But once margins on the hardware hit zero, the cost moved to you.
In Q3 2024, Vizio lost $6.7M selling TVs and made $115.8M in gross profit from ads and viewing data [3]. They've said on earnings calls that they keep TV prices low to grow the audience they sell to advertisers. Walmart bought them in 2024.
This isn't a conspiracy theory either. Vizio paid $2.2M to the FTC in 2017 for tracking 11 million TVs without consent. Last December, Texas sued Samsung, LG, Sony, Hisense and TCL over ACR. Samsung and LG have since agreed to stop collecting that data without explicit consent [4].
TL;DR
1. ACR off
2. Ads + voice off
3. Smart devices on their own network
4. NextDNS filtering on the router
Sources:
[1] ACR study: arxiv.org/abs/2409.06203
[2] Cost of US consumer goods: aei.org/economics/chart-of-t…
[3] Vizio Q3 2024: sec.gov/Archives/edgar/data/…
[4] Texas v. Samsung: texasattorneygeneral.gov/new…
i own a relatively new (2025) samsung tv.
i kept getting weirdly targeted ads.
i tried reversing the firmware but it was aes encrypted and no keys unless tear it apart and do uart/jtag magic.
zero days it is. root shell on new samsung TVs!
discovered PRIVACY HORROR. write up?
Okay, since the news is already out: an RCE vulnerability in PHP core, CVSS 10.0. Further details are scheduled for release on October 20. Only PHP 8 will receive patches.
The potential impact of the ConnectWise supply chain attack is massive.
One compromised OAuth application with elevated permissions could give attackers access to emails, files, and directory data across hundreds of Microsoft 365 tenants.
Even worse, attackers could establish persistent access by adding credentials to other applications, surviving the revocation of the original compromised credentials.
And with MSPs involved, the potential blast radius could extend even further to downstream customers.
We don't know the full extent of the compromise yet, but this could affect far more organizations than those directly using ConnectWise Cloud Backup.
linkedin.com/posts/microsoft…
If AI didn’t exist and I came to the infosec community and said “here’s a magic box that finds 0days” and “here’s another box that can autonomously scan networks for misconfigurations”, they’d be jumping up and down to see if we could glue together a self-replicating worm. 1/
it's funny how hard it is to get a text editor out of any of the ai tools now - even @cursor_ai. we’re in this weird teenager phase.
moving from coding to systems engineering.
security engineering is real and effective at containing intelligent agents. we're going through a big evolution right now but the fundamentals are still... fundamental.
I really need more big names in cybersecurity to come forward and state the obvious: cybersecurity is real and works and yes we absolutely can contain an AI even if it’s extremely good at finding zero days.
Anthropic published real AI intrusion data that probably deserves more attention than speculative concerns over the probability of AI doom.
Both concerns can coexist, but one has practical risk that directly impacts most enterprises in the short-term -- whereas the other should probably dictate how the AI labs [are forced to] behave
Anthropic has now published their side of this APT29 🇷🇺 cyber espionage campaign, complete with a timeline of capability development & intrusions: anthropic.com/threat-intelli…
...helpful data to support prior comments about Midnight Blizzard's CaptiveCrunch being enabled by AI