BBcan177 (@BBcan177) header
BBcan177 (@BBcan177) profile picture

Dev of pfBlockerNG | #pfBlockerNG | #pfBlocker | |/r/pfBlockerNG |

Canada
Joined May 2016
BBcan177 retweeted
Earlier today, Optimizely identified and contained a security incident affecting some Optimizely Web Experimentation customers. The vulnerable path is blocked, the injected code was removed, and customers have been contacted directly. Updates: status.optimizely.com
32
49
29
147
76,357
Security Onion 3.4.0 is now available, including Agentic AI Automations! This release contains many updates, features, and quality of life improvements - more information in the blog post linked below.
2
14
2
42
3,657
Someone has created a vulnerable PHP website, loaded it with a Bitcoin wallet, and challenged the Internet to hack into it and they can keep the Bitcoin. It has a running timer to show if the PHP exploitability was over-hyped. stealmybitcoin.com/
177
460
146
7,085
2,848,945
BBcan177 retweeted
300k commits to Easylist!
4
5
1
24
671
Just found a zero day If you right click on an executable on Windows, select run as administrator, it will run as administrator I'm calling it Program2Shell
195
513
47
11,178
220,777
Lol
Ugh now we have html2shell?
4
482
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,694
Set session.upload_progress.enabled=0 till next PHP release to block an unlikely RCE vector (CVE-2026-115560). Already recommended for CVE-2026-109619 Wed, keep disabled. Only apps with non-default serialize_handler switching it to "php" at runtime can be affected. #php #phpc
52
903
151
2,842
412,144
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
285
3,257
675
22,572
2,283,640
BBcan177 retweeted
We launched OSS Scanner, which gives critical open source projects free, periodic vulnerability scans from our strongest models. Each finding includes a proof-of-concept, and a patch where possible. red.anthropic.com/oss-scanne…
289
1,331
332
13,704
1,176,884
You can use our hosted MCP server (mcp.ipinfo.io) or host it yourself: github.com/ipinfo/mcp
2
6
208
We reduced our MMDB file sizes by 31% across 89 databases, with savings up to 80% for individual files. Same data. Same lookup results. Smaller memory footprint. Here's how we did it, and why we open-sourced the tool → ipinfo.io/blog/how-made-mmdb… #OpenSource #MMDB #IPData
4
6
443
BBcan177 retweeted
The phishing ecosystem increasingly runs on legitimate infrastructure. See which free hosting solutions were most frequently abused in attacks targeting the U.S. financial sector and what the trend reveals about modern phishing operations. eu1.hubs.ly/H0yHxXW0
2
2
152
BBcan177 retweeted
Consider this a first draft, I have way more notes about other things to add at some point. It's also a little bland, but one thing I'm not is a designer. Let me know about any issues. It's on GitHub too, so PRs are welcome. github.com/pgl/dns-museum
1
1
200
BBcan177 retweeted
find 0day, spin up 4 subagents, keep them in the sandbox
Bro stuck in infinite loop
4
18
2,080
BBcan177 retweeted
Weekly block list report: 3,548 entries; 3,516 valid / 32 invalid; 9 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport List URL: pgl.yoyo.org/as/serverlist.p…
1
1
252
INTEL DROP A single range 185.177.72.0/24, running a continuous live web-exploitation campaign. 22 IPs, and the block is defined by what the hosts do rather than any one malware family. -19 are flagged for path-traversal -18 for active-exploitation -18 for wordpress-enum -12 for command-injection After researching in OSINT we see @GreyNoiseIO in March 2026 was first to observe and post. Resurfacing because the activity continues. Attacking hosts: 185.177.72.5 185.177.72.9 185.177.72.11 185.177.72.12 185.177.72.13 185.177.72.17 185.177.72.22 185.177.72.23 185.177.72.29 185.177.72.30 185.177.72.38 185.177.72.53 185.177.72.54 185.177.72.56 185.177.72.58 185.177.72.66 185.177.72.67 185.177.72.68 185.177.72.69 185.177.72.70 185.177.72.100 185.177.72.205 Tightest run: 185.177.72.66 through 185.177.72.70, five sequential hosts sharing the same path-traversal and active-exploitation profile. #TotalInsights #ThreatIntel team-cymru.com/total-insight…
12
38
2,232
Replying to @NetworkChuck
YES! Once the bills are paid, money only buys you comfort and comfort is numbness. Buy the ticket, take the ride, use your wealth to live a life less than ordinary, use it to empower others and do great things. Life isn't measured in dollars or time, but experiences.
1
7
422