DenverSec (@DenverSec) header
DenverSec (@DenverSec) profile picture

DenverSec is a #CitySec gathering for anyone interested in information security. Usually every third Wednesday in Denver at 7PM. [email protected]

Denver, CO
Joined June 2014
Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)Photo by DenverSec (@DenverSec)
I think there’s a fundamental misconception in how the security industry talks about ARTEX, Cairn and similar offensive AI frameworks. And even reports from major security vendors keep reinforcing it. People treat these frameworks like the C2 frameworks we’ve known for years. With Cobalt Strike and others, parts of the framework were deployed on the victim’s systems. Implants, loaders, communication protocols and other implementation details provided recognizable patterns that we could write signatures for. But ARTEX and Cairn work differently. The orchestration runs on the attacker side. The LLMs, prompts, skills, tools and infrastructure are interchangeable. Change any of these components and the resulting attack can look completely different. The framework itself doesn’t define what ends up on the victim’s systems. Yes, there are a few minor implementation fingerprints, such as certain ARTEX/Norma User-Agent strings. We’ve even written rules for them. But these cover tiny parts of a framework’s functionality, not the attacks it can orchestrate. An IP address, webshell or exploit used in a campaign doesn’t suddenly become an “ARTEX indicator” because ARTEX was involved. And that’s why I find all these “ARTEX IoC collections” and “How to detect ARTEX” guides so misleading. They encourage people to think we’re dealing with another recognizable malware or C2 framework. We’re facing a different class of offensive technology, and I think many people still haven’t understood that. The detection guidance should be what we’ve been telling defenders for decades: detect malicious behavior, attack techniques and traces of compromise. There is no special defense against ARTEX. Tomorrow the same attacker could use a different framework, a different model and completely different tools. The names are disposable. The underlying attack techniques are what we need to detect.
34
107
17
508
39,215
This week has been quite a shitshow already, and there are still 2 days to go Here’s a quick recap of the security mess we’ve seen in just the last few days: 1. PHP Core RCE (CVSS 9.2) Two critical vulnerabilities (CVE-2026-109618/109619) allowing unauthenticated RCE. A huge number of PHP installations potentially affected, and there are already reports of reliable exploitation against patched versions. Great… Useful links: Official PHP advisory and patches: php.net/archive/2026.php#202… Practical hardening and mitigation guide by Vincent Schmalbach. nginx/Apache configurations, PHP settings, patch verification and compromise checks: vincentschmalbach.com/cve-20… Huntress analysis. What to monitor, suspicious child processes, webshells and post-exploitation activity: huntress.com/blog/php2shell-… Wiz technical deep dive. Exploit mechanics, memory disclosure, affected applications and the role of AI: wiz.io/blog/php2shell-php-rc… Corelight’s open-source Zeek and Suricata detection rules: github.com/corelight/php2she… 2. GitLab RCE (CVSS 10.0) CVE-2026-110264. An integer overflow in the regex compiler leading to unauthenticated RCE. Apparently affects around 12 years(!) of GitLab releases. docs.gitlab.com/releases/pat… 3. Node.js / Brotli RCE CVE-2026-111497. An out-of-bounds write in the Brotli decoder that can lead to RCE when processing malicious compressed data. Node.js 22, 24 and 26 affected. nodejs.org/en/blog/vulnerabi… 4. DNS-over-QUIC DoS CVE-2026-97206. A use-after-free in Unbound’s DNS-over-QUIC implementation. Remote attackers can crash affected multi-threaded DNS resolvers. nlnetlabs.nl/projects/unboun… 5. eMudhra CA disaster And then there’s this absolute PKI clusterfuck. Eight intermediate CA private keys turned out to be ridiculously easy to reconstruct. Browser vendors have started blocking the affected CAs, but outdated clients and applications with their own trust stores could keep accepting certificates from them. Cleaning up this mess is a lot harder than just patching a server. Google’s analysis and response: blog.google/security/protect… Mozilla’s public incident investigation, including the technical findings, timeline and eMudhra’s explanations: bugzilla.mozilla.org/show_bu… — And I can’t help wondering how much of this sudden wave of discoveries has to do with the latest AI models getting better at code review and vulnerability research. We now have models that can dig through massive codebases and potentially find bugs that have been sitting there for years. I’m not saying these particular vulnerabilities were discovered using AI. I haven’t seen evidence for that. But I do wonder whether we’re starting to see some of the effects. The eMudhra case is obviously a different story. That’s a spectacular failure of key management and quality control. Anyway, quite a week. And it’s only Thursday…
🤖 Made with AI
42
180
16
633
74,506
DenverSec retweeted
What the TV does by design: — scans your entire home network continuously. in their test: one TV identified 38 unrelated devices including phones, smartwatches, printers, and thermostats belonging to people not involved in the test. — collects the names and signal strengths of every nearby WiFi network, plus location data. all sent to LG Ad Solutions. — runs ACR (Automatic Content Recognition) on everything displayed on screen. including HDMI inputs. your laptop, gaming console, or work monitor connected to the TV is being fingerprinted. — one TV exchanged roughly 4GB of ACR-related data per month. What the TV does that LG says it doesn't: LG publicly stated their TVs "do not collect, record, or store ambient conversations." Gamers Nexus found: — the TV converts speech to plain text and stores it in on-device logs — the microphone window stays open 10 to 15 seconds after talking stops, capturing bystanders who never addressed the TV — the TV recorded room audio while the screen appeared off and the Ethernet cable was unplugged, then exfiltrated the file the moment it reconnected The security vulnerabilities on top: Beyond the designed behavior, researchers found remote code execution vulnerabilities in webOS that could allow a compromised TV to be weaponized as a covert listening device. these sets are in hospitals. waiting rooms. boardrooms. hotels. a surgeon asked Gamers Nexus where that leaves patient confidentiality. Gamers Nexus has no answer. neither does LG. What to do right now: — disconnect your LG TV from your network entirely. route streaming through an Apple TV, Roku, or Fire Stick instead. — if you must keep it connected: put it on a separate IoT VLAN or guest network so it cannot reach your other devices. — disable the built-in microphone in settings. — check your privacy dashboard and opt out of ACR and ad personalization. — after every firmware update: recheck all of the above. Credit to Gamers Nexus, Level1Techs, and other independent researchers.
Your LG Smart TV might be more interested in what’s happening in your living room than you are: Researchers found tested LG TVs scanning local devices, capturing microphone audio in standby, and storing data until they reconnect to the internet.
200
2,189
226
10,878
3,086,965
We've got a new logo for our 2026 conference! The BSides Boulder CFP is still open for two weeks. Submit your conference talk on Sessionize: sessionize.com/bsides-boulde…
3
7
230
Got a great cybersecurity talk you want to present? #BSidesBoulder26 Call For Papers (CFP) is open! This year, we are changing things a bit...accepting full track talks (50min) and half-track talks (25min), so bring us your war stories, insights, and novel ideas!
1
2
3
99
I think this is a great article from @arstechnica going through the #Signal #quantum #crypto hardening. I will be honest in saying I had not read up on the ‘ratchet’ key system. Many more details at the @signalapp website. arstechnica.com/security/202…
1
2
109
"Plex Urges Password Resets Following Data Breach: Hackers accessed emails, usernames, password hashes, and authentication data stored in a Plex database." securityweek.com/plex-urges-…
1
2
164
Going to be at @defcon 33? Our conference tshirts are great for getting your wardrobe prepped for hacker summer camp. Send us a photo if you spot a #BSidesBoulder shirt this summer!
3
2
406
Yo, do you wanna do some Hacker Jeopardy with me? I'm good, team I was on took 2nd at DerbyCon 9 but I've never had a chance to play at #Defcon. Hit me up if you want to do this, and if not, RT this so hopefully I can make this dream happen. Bonus, if you're on my team, You're a badge.
4
4
5
437
Remember #denver that we have #BikeToWorkDay #Summer tomorrow! Sign-up to let them know you are participating, and check out the food or drink stations that you might have along the way. drcog.org/bike-to-work-day Bike to Work Day Summer | Denver
1
1
79
Our stream for today's conference is live! youtube.com/watch?v=HOG7Q7lI…
3
4
216
Incoming shorthand...Tomorrow's #BSidesBoulder25 is sold out! Walk-ins may be available, no guarantee of a shirt, official stickers, or sandwiches. TL;DR topical blurbs: —🆕 Sticker swap table + mini-lock picking village. —📢 Day of comms. We will use non-LinkedIn social media
1
2
2
190
💥🖥️ Don't miss Nathan Montierth's #BSidesBoulder25 talk "Navigating the Virtualization Battlefield: A Deep Dive into Hypervisor Attack Vectors", which plans to explore how attackers are breaching hypervisors (think ESXi, Active Directory, and more), and what you can do to fight
1
1
1
112
Tickets are now on sale for our #bsidesboulder annual event on 13 June! Your ticket purchase comes with lunch and a t-shirt. We expect our @KC7cyber CTF workshop will sell out given the limited seats, so get your ticket now. eventbrite.com/e/bsides-boul…
11
5
3,690
Woah, August snuck up on us! We almost forgot to light the beacons and announce to the world that BoulderSec is this week! Specifically, this Thursday at 7:00pm at the Rayback Collective.
2
2
3
215