Jered Bare (@jeredbare) header
Jered Bare (@jeredbare) profile picture

^ Not my profile pic InfoSec, Fitness, and Python. Expect delays.

Joined March 2009
Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)Photo by Jered Bare (@jeredbare)
Jered Bare retweeted
The watchTowr team is currently rapidly reacting to the newly published "NGINX2root" Remote Code Execution vulnerabilities, including CVE-2026-123633 and others in NGINX's HTTP/2 handling. Active watchTowr Platform clients are being made aware of their exposure.
4
17
1
67
7,571
Jered Bare retweeted
With all the outages happening, it's hard to not lean towards something larger happening. We still have no evidence of mass outages caused due to cyber. The FBI warning around ARTEX was more of an advisory around it being used by threat actors doing active campaigns, not disruption efforts. Most folks don't realize that our interconnected systems, predominantly because we put all of our eggs in large baskets causes much of this. Instability in large cloud providers cause not one outage, but thousands if not hundreds/millions of outages as we saw last week with Microsoft. I know folks in almost every organization that has been impacted here, folks I've known for years - all confirming it was not cyber-related. In stating that - is it possible? Absolutely. However, a lot of what we are seeing is hyper sensitivity - any blip is going to cause a reaction right now. Again, can't rule out cyber attacks in any stretch, and I'm deeply concerned on what we are seeing across the spectrum from a security operations perspective and incident respond side. It is definitely elevating upward for data breaches especially with autonomous attacks. The next 6 months are going to be rough, at the same time - we will always find a way to get better, improve, make these less impactful. I want to emphasize again, none of these outages have been confirmed a cyber attack and have clear explanations on what has happened. Which honestly, should concern us more. It's showing how weak our infrastructure in supporting our daily lives really is, and how that can change very quickly. We must do better.
56
72
10
373
25,262
Jered Bare retweeted
the dumbest people you know- “let me REALLY tell you what’s going on with NSANet”
11
20
1
213
7,054
Jered Bare retweeted
I'll be on @CNN around 7PM ET today talking about the FAA outage. First - no-one knows what happened, not even the FAA, the FBI, or anyone else. These things take time - so anything is speculation and not conjecture. Second - the FAA systems are super old dating back to the 1980s with STARS deployed in the 2000s to 2015. The new AI systems being deployed The GAO has every year stated the FAA is in a dire straight for reliability (and security). FAA’s 2023 assessment classified 105 of 138 systems, about 76%, as unsustainable or potentially unsustainable. As of September 1, 2026, FAA said it had replaced over 64% of its copper-based TDM telecommunications infrastructure, leaving roughly a third awaiting replacement. The modernization plan also illustrates how much equipment needs work. It covers 450 legacy voice switches, digital radio conversion at 1,581 sites, 612 radar replacements, and 53 surface movement radar replacements. Those are program totals, not counts of what remains today. Most of that work targets completion in 2028. A new system called SMART (AI-based) has been used in limited capacity. SMART began limited operations around Washington, D.C., in September. On November 10, FAA announced its expansion to airspace managed by all 22 air route traffic control centers. If cyber-related (which again no-one knows) - more modern systems require substantially more interconnected systems that if not properly introduced, can increase attack surface by allowing multiple communications in through third parties, other networks, and less network segmentation versus the older system which was highly segmented from public Internet. My predictions (purely speculation) - if not cyber related, flights resume tomorrow. Will cause massive flight disruptions for a week or so. If cyber related - flights probably resume on Monday or later.
44
68
8
358
46,886
It’s clear that Microsoft is struggling as a result of not replacing enough employees with AI. Look at this grammatical error. They couldn’t even make it to 20 hours of nonsensical corporate slop posts about their outage without a grammatical error. Copilot would never 💔
Replying to @MSFT365Status
We're engaged in multiple workstreams to alleviate impact, address our current blocker, and returning portions of service infrastructure back to a healthy state. A more comprehensive update can be found at MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
12
47
3
669
31,121
Would you look at that. Binance was hacked via phishing (Contagious Interview), not zero-day exploits written by abliterated AI models. Exactly as I predicted. I may shitpost a lot, but I do actually know some things about some stuff.
Replying to @GergelyOrosz
How many attacks have actually been attributed to AI zero-days at all? And how many of those were attributed to abliterated open-weight AI models? Binance was more likely than not, the result of just boring old phishing. That is the most common technique that attacker uses.
49
176
15
1,225
47,644
Jered Bare retweeted
Honestly, if you read just one thing today, please read the annual report from @NCSC In a sea on hype, this is an honest, sensible view of the world! A great job from the team! #UK #Cyber #NCSC #DefendAsOne #Security #AI ncsc.gov.uk/collection/annua…
9
62
2
300
16,701
Honestly, I give up at this point. There is zero information out about the hack, other than the fact it was Trader Traitor (North Korea). Yet NYT have not only already decided it was AI, but that it's part of *a new era!* DPRK has been looting crypto exchanges since 2016. Their go to technique is phishing. Nothing they do requires AI, nor would it meaningfully benefit from adding AI. They also hit less platforms in 2026 and 2025 than they did in prior years (4 in 2026, 3 in 2025, 6 in 2024, 8 in 2023). Every hack is just AI now. Nobody did hacking before AI. It's the only way to get into systems. If the hack turns out to be AI, it was AI. If it turns out to not be AI, it was still somehow AI. There is no hacking, only AI.
47
118
10
802
36,332
Full blown intrusions happening for php2shell right now, which you can watch here: php.events.greynoise.io/ It looks like the actor intends to deploy ransomware. It also looks like they have compromised other actually real victims.
11
57
2
274
29,447
American glass. American metal. American silicon. American batteries. American workers. American everything. BlueChip is the first American computer in decades. Don't let anyone lie to you and say it can't be done. Designed in California. Built in America.
BlueChip. Built in America. America made the first electronic computer to win a war. Now we depend on our greatest adversaries to build the computers that run our economy and defend our nation. Today, we bring it home.
1,360
4,404
417
49,879
1,405,856
Jered Bare retweeted
you don't need daybreak, you need to segment your fucking network
20
25
4
351
16,460
Jered Bare retweeted
As someone who builds what I think is considered a “defensive swarm” product, a big part of my bet is that Nikesh (Palo Alto Networks CEO) is wrong. The token economics are increasingly in our favor. You really can throw tokens at logs.
30
8
2
137
10,515
Jered Bare retweeted
We’ve seen plenty of people try to vibe code the php exploit who have no experience in the domain. Failure. Over and over. Then people who know what they are doing in exploit dev, marginal success. People would say anyone with a frontier LLM can just say “hack this site, make no mistakes” and I won’t argue, some shallow bugs will fall out this way for a while. But the most successful applications of LLMs are coming from experts who at least know how to dissect the problem, change the models thought direction, and have put engineering into harnesses and skills. I’ve seen this across several sub sections of cyber. And that requirement will only get more mandatory as all the shallow bugs shake out. Just my 2c and observation. 🫶 (Also beware of influencers trolling with opinions on this topic. It’s often just for fake clout and clicks)
39
60
7
482
23,959
Jered Bare retweeted
it all comes down to reducing your internet facing attack surface as much as you can
10
3
2
46
3,047
Jered Bare retweeted
Because again as we have been trying to tell everyone, they are NOT inventing anything new, but are instead using the techniques we hackers either invented or have been using for years. Neat little trick. Not novel. They fed the model our notes along with every other piece of information throughout human history. All they are doing is repackaging that or repurposing it.
Replying to @scaling01
Cool but that's also a decade old, well-documented technique so we can assume agents will get good at every method used before, at minimum.
7
25
2
144
3,748
Jered Bare retweeted
its almost 90 days later. I submitted a blind ssrf that allowed me to enumerate an internal network for @Meta who rejected it because @ManusAI left their portfolio. I contacted @ManusAI about it, and their internal AI just kept telling me it referred it to Security then closing the ticket over and over. If someone from Manus wants to talk, lmk. Otherwise I will be writing up the finding for next week.
1
3
11
624
Years ago I challenged our community to do a better job at characterizing exploitation "in the wild." There's lots of reasons for why, but the primary reason at the time is security researchers were using "in the wild" as the signal that it was low to no risk to publish offensive capability. "In the wild exploitation" at one victim in one country is not anywhere near the same "mass exploitation." PHP2SHELL is a good example of where there are private exploits that are not publicly available, and there are less potent exploits that are, and there's mass exploitation *attempts* using these less potent exploits and they aren't really working in real scenarios relative to the volume of attempts. Does that matter? It does. It's bought a lot of time for down stream would be victims to put durable mitigations in place.
5
7
2
48
3,286
I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain: Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either: a) a world-class exploit developer with an extreme case of imposter syndrome. b) currently looking at some very confident-sounding but wrong LLM output. I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works. I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself). The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off". People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media. So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector. What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't). The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations. LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.
138
581
108
3,630
363,748
Jered Bare retweeted
I love the “anyone can write an exploit with an LLM and hack everything now” narrative. Feel free to poke around GitHub for php2shell and see how many of those PoCs work outside the Docker container they were built on. There are a few working ones in that sea of broken/lab only PoCs, but oddly enough, the people who wrote them actually knew what they were doing.
12
19
138
6,694