Phill (@Savphill) header
Phill (@Savphill) profile picture

Web dev & security tinkerer (CVE-2025-58674 among others). Now planning corporate offsites for remote teams.

Thailand
Joined August 2021
Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)Photo by Phill (@Savphill)
Wait until he finds out that North Korean hackers actually went after banks before moving to crypto. They looted the Bangladesh Central Bank for $1 billion. The transfer got caught and reversed because the street address of the bank they tried to wire the money to had the same name as a sanction Iranian oil tanker, and OFAC sanctions basically run on RegEx, so they accidentally froze the transfer for sanctions evasion.
After crypto exchanges fall, banks are next. Black hat hackers are getting ready to attack them with AI swarms. In fact, they are already running live tests on banks around the world. There is no such thing as a system without flaws, and no asset is truly safe anymore. They are not just going after the money. The plan is to attack the banks and shut down the whole internet at once. Attacking is always way easier than defending. Even with AI swarms on defense, defenders have to block every single angle. Attackers just need to find one open crack. Not trying to be a doomer here. Just looking at what is already playing out in the wild.
23
156
7
1,510
65,182
Phill retweeted
24 hours ago I built honeypots directly into my live web servers. There has been over 60 attempts of php2shell on the servers. Out of those 60, none of them have been done correctly. Here are two examples
8
11
2
124
12,915
For comparison I checked with the Wordfence team and we saw 5 site cleanings for the UpdraftPlus infrastructure compromise 6 days ago. And that WordPress plugin has 3 million installs. BuiltWith says there are 23 million or 104 million PHP sites, depending on whether you count 'expired' or not. And not a single compromised site hit our site cleaning team. 🤔 teapawt.net/mmaunder/status/211335…
We protect over 5 million PHP sites and when we find a major exploitable vulnerability, we always see site cleanings. We have seen exactly zero hacked sites from php2shell. Zero. Across a population of 5 million PHP sites that our product protects. Draw your own conclusions. #php2shell
2
3
1
12
3,558
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,631
363,718
Same vibes
BBC: Hablaremos con nuestro experto en seguridad de BBC respecto a la vulnerabilidad de PHP. El experto en seguridad: No sabía que PHP existía hasta ayer en la mañana.
13
113
2
1,155
31,744
We protect over 5 million PHP sites and when we find a major exploitable vulnerability, we always see site cleanings. We have seen exactly zero hacked sites from php2shell. Zero. Across a population of 5 million PHP sites that our product protects. Draw your own conclusions. #php2shell
55
117
44
1,014
236,034
Replying to @Denche2005
php is the kitchen that cooks food for a lot of websites. someone found that if you shout a large order, the cook panics. then stranger can walk in and put something rotten on plate waiting to be served to a customer.
41
171
25
5,818
341,323
The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.
337
4,158
1,254
18,526
7,098,118
Phill retweeted
Please update your sites ASAP. The unauthenticated stored xss one can be reproduced in a stock install (comment moderation is off by default and previously made comment config can be bypassed) CVE is still in process.
1
2
296
I read @DarioAmodei's essay calling on the labs to pace the frontier. @sama agreed. The frontier will move at whatever speed it moves. The rest of the world will not slow down. Our job in the cybersecurity community is to make sure it moves securely and safely. Here’s what I see from the front lines: 1. The unit of threat is no longer the hacker. It's an autonomous campaign. I call it the Agent-state. We see coordinated AI agents executing attack campaigns at machine speed. 2. Sophistication is dead as an attribution signal. AI gives every criminal and lone actor elite execution. Identity, infrastructure, and intent tell you who's behind an attack. Skill doesn't. 3. Runtime is the control point. Endpoints, cloud workloads, and SaaS are the battleground. Governance documents don't stop an agent in motion. Enforcement at machine speed does. 4. Every AI agent is a privileged identity. Least privilege, short-lived credentials, traceable actions, and a kill switch. Permissions never expand because an agent decides it needs more. 5. Defense has to be autonomous but also bounded. Machine-speed response, tiered by consequence, with humans owning the high-impact calls. 6. Every failed attack should make every defender smarter. Feed what we block back into detection, across customers and models, with privacy intact. This is what CrowdStrike and NVIDIA introduced with SafeMind: an agentic, always improving model and harness protection system built for defenders. 7. The AI industrial base is critical infrastructure: weights, training clusters, APIs. Call it what it is and protect it like it is. Pacing what comes next doesn't secure what's already here. The credible path is to deploy with proof: board-level accountability for AI security, independent external red teaming, incident disclosure, secure defaults, and controls that work in production - not on paper. Anthropic and OpenAI just committed to embedding independent evaluators with employee-level access. CrowdStrike will bring what we see from the front lines to that table. The ability for AI to act must be matched by the ability for defensive AI to stop the breach.
We Must Pace the Frontier: I’ve written a new essay on why the AI industry should slow down, with a three-part plan for doing so. Anthropic is unilaterally committing to the first of these steps. We’ll provide third-party evaluators with permanent, employee-level access to our systems, so that they can verify adherence to our safety measures, report on incidents, and assess models’ alignment during training. You can read the full post here: darioamodei.com/post/we-must…
171
203
65
1,396
1,027,551
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
20,368
166,568
39,481
799,141
175,788,803
Thank you GOOGLE for finally giving us AI Search performance data #SEO ♥️🥰
JUST IN 🚨 Google to show AI Search performance data in Search Console #SEO "To help you understand how pages from your site are shown, our new reports show the following information: Impressions: How often URLs from your site appeared in generative AI features in Search and Discover. Pages: Check which URLs appeared within AI features. Countries: Understand your visibility on a country basis. Devices: Identify the devices people are using when seeing your website (available for Search results). Dates: Monitor your performance over time with hourly, daily, weekly, and monthly granularity."
8
7
1
163
43,812
Anthropic onboarding day: Michael Scott introducing Karpathy like he just signed Wemby in free agency.
389
1,464
375
17,589
2,484,251
WordPress 6.9.2 is now available. This security release addresses 10 vulnerabilities, including stored XSS issues, an authorization bypass, and a path traversal fix. Update your sites as soon as possible. wp.me/pZhYe-5eS
5
38
9
114
14,737
React researchers right now
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
9
90
3
1,256
53,091
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
6
90
2
1,409
53,036
Phill retweeted
Researchers have found two new vulnerabilities in React Server Components while attempting to exploit the patches last week. These are new issues, separate from the critical CVE last week. The patch for React2Shell remains effective for the Remote Code Execution exploit.
385
1,169
1,446
6,241
3,261,974
This movement works because companies step in. If you’ve ever wanted your business to support a cause, this is your moment. Join #WPGivesAHand: buff.ly/xXgwAgw
3
3
236
Happy Birthday PHP 🎂🎉
10
182
11
1,020
41,181