Pinned Tweet
Dunk’s Mantra: I don’t care if you’re black, white, brown or sky-blue pink with yellow dots on. I also don’t give a shit what you’ve got between your legs or what you do with it, as long as it doesn’t involve animals or kids. And whatever you ‘identify’ as, you’re human to me. 🤗
3
16
Worth a read. Dragos researchers intentionally sent messages with canary credentials to different LLM services. In several cases this lead to a compromise because of rogue services or existing unidentified compromise of the provider.
We seeded 2m canaries into popular AI services and tracked where they were stolen and abused.
This identified:
- Three compromised providers
- Resellers stealing prompts via built-in logging
- Providers ignoring ZDR & privacy flags
dragos.com/blog/ai-supply-ch…
D:\unk.osint retweeted
Oh, boy, this vCenter bug is nasty. Admin access without credentials, and already exploited back in September(!)
Mandiant’s report shows how the attackers went on to steal data directly from VM disks. Plenty to worry about here, even if your vCenter isn’t exposed to the internet.
I wouldn’t leave this for the next regular patch window.
cloud.google.com/blog/topics…
github.com/vmware/vcf-securi…
cve.org/CVERecord?id=CVE-202…
What I don’t get: Broadcom credits Mandiant for reporting this bug, but leaves out the exploitation in the wild. 🙄
Meanwhile, Mandiant publishes evidence of attacks going back to September(!). That’s information customers need when deciding how urgently to patch.
D:\unk.osint retweeted
HackerGadgets Releases a 4-in-1 RTL-SDR, LoRa, GPS and RTC HAT for the Raspberry Pi rtl-sdr.com/hackergadgets-re…
D:\unk.osint retweeted
Fieldwatch 1.2.0 is now available.
Fieldwatch is a free Android app that shows you what's watching you. It can flag nearby Ray-Ban Meta glasses, Flock cameras, body cams, public safety vehicles, drones, and a lot more. It spots Bluetooth trackers like AirTags that are moving with you, and its Hunt tool helps you find one if it's hidden. It can also warn you about odd cell tower changes or GPS interference.
New this release:
Drone perimeter detection. Because drones fly high, your phone can hear their Remote ID from up to several miles away. You don't need a ping for every drone on the horizon. Pick your distance, like 250 m, and Fieldwatch draws an invisible dome around you. When a drone's broadcast position comes inside it, your phone alerts you.
Drone swarm detection. If several new drones pop up at once, Fieldwatch alerts you. Five or more in half a minute is unusual, so when it happens, you'll know.
Quickly see where it's headed. Tap a drone's Remote ID marker on the map to see its altitude, speed and course without having to pull up all details.
A bigger view of your sit. The Sit Paths map is now larger, so you can now better see the whole route and every detection along it.
Low battery protection. When your battery gets low, Fieldwatch slows its scanning. If it gets lower still, it stops, so you keep enough charge for maps, calls and TAK.
329 signatures and counting. Fieldwatch now names more of the devices that used to be unmatched. More two-way radios, smart glasses, thermal optics, FPV drone radio links, dashcams, cars, and a long list of everyday gear.
Share signatures with any app. Exports and imports now speak Radio Signature Interchange (RSI), an open standard for describing radio devices. It covers frequencies beyond Wi-Fi and Bluetooth, so it works for ESP32 projects, SDR setups and external radios attached to a phone.
Please encourage the developers of the other radio apps you use to consider adopting RSI. Any app that does gets all 329 Fieldwatch signatures right away. More at github.com/OffGridPete/radio…
Get Fieldwatch on Github at:
github.com/OffGridPete/Field…
D:\unk.osint retweeted
Windows 11 26H2 lockscreen has been bypassed, this allows a full bitlocker bypass.
github.com/MSNightmare/FastU…
D:\unk.osint retweeted
🚨 **WHO IS BEHIND THE MACHINE MOBILISING BRITAIN’S ANTI-FAR-RIGHT PROTESTS?**
Meet **SMALL AXE COMMUNICATIONS LTD**.
Company number: **07877552**.
This London-based campaigning organisation openly describes its role in building and mobilising the **Together Alliance** demonstration on 28 March 2026.
And the scale is staggering.
According to Small Axe’s own figures:
🚍 **136 coaches** coordinated nationwide
🖨️ **750,000+ printed campaign materials**
🏢 **500+ organisations** brought together
📱 **11 MILLION+ social media impressions**
📧 **28,000+ active email supporters**
🗳️ **68 MPs** became co-signatories
🗺️ Interactive transport maps, mobilisation toolkits, fundraising systems and coordinated messaging.
And who appears among the Alliance’s supporters?
**Stand Up To Racism, the TUC, UNISON, GMB, National Education Union, Greenpeace, Care4Calais and others.**
But here's another interesting detail.
An Electoral Commission record contains a **£84,870 invoice from Small Axe to the National Education Union in June 2024** for campaign support on Stop School Cuts.
That's a separate campaign, not evidence of funding for Together Alliance. But it demonstrates the scale of paid campaigning services Small Axe provides.
**This is professional, nationwide political mobilisation, not simply a few people turning up with homemade placards.**
Organising lawful protests is perfectly legitimate.
But the public deserves to know:
💷 Who commissioned and funded the 2026 campaign?
💷 How much was spent on printing, advertising and digital campaigning?
💷 Who financed the transport arrangements?
💷 Which organisations contributed money, staff or resources?
**When a political movement operates on this scale, transparency matters.**
And we should be following the money.
🔎 Small Axe’s own case study:
thesmallaxe.org/project/toge…
🔎 Companies House: 07877552
🔎 Electoral Commission invoice:
search.electoralcommission.o…
D:\unk.osint retweeted
A missing person. A locked trail of evidence. Details waiting to be connected.
A new narrative-driven OSINT challenge from ShadowDragon® is coming December 1.
What will you look for first?
#CaseTrace #OSINT
D:\unk.osint retweeted
🚨‼️BREAKING: Clown2shell exploit where u where u umm play urself bcause u keep reading cveslop nd u think oh wow am i pwnd nd u keep trying to patch but it ddoses u nd that lets the hackers in bcause ur too busy juggling dogshit. read more on wiz blogpost
D:\unk.osint retweeted
PHP2Shell, Java2Shell, Nginx2Shell… WHAT THE ACTUAL FUC# IS WRONG WITH YOU PEOPLE? These AI toys have driven you completely insane. GET A LIFE. GET MARRIED. TOUCH THE GRASS. SEE A THERAPIST. NOT EVERYTHING NEEDS A FUC#ING SHELL!
D:\unk.osint retweeted
So the last one was PHP2Shell, this time it’s going to be:
1. PHP4Shell
2. PHP2Shell Reloaded
3. 2Shell2Furious
4. PHP2Shell 2: Shell Harder
php.net/archive/2026.php#202…
D:\unk.osint retweeted
Oh, great, now we have Nginx2Shell..
It's only Wednesday, can we please chill?
D:\unk.osint retweeted
I've been sent the initial Incident Report from Optimizely.
There are some interesting details in the report, but two main concerns jump out at me.
1. We have confirmed infections outside of their timeline. They state first infection at 07:51 but we have infected files at 04:21 and 03:55.
2. Their IOC list contains domains we did not see used in this attack, and it doesn't contain any of the domains we did see.
pages.optimizely.com/rs/947-…
D:\unk.osint retweeted
Want to watch an electrical grid get hacked in real time? ;)
We simulated an electrical substation, then ran a Sandworm (APT44) inspired attack against it.
Starting with an edge device compromise, we moved through the IT network, crossed into OT, reached the substation controls and tripped the circuit breakers.
Watch the breakers open and the simulated city go dark.
xintra.org/research/simulate…
You can explore this environment in @XintraOrg Twin, and a version will also be published on Labs.
D:\unk.osint retweeted
nginx2root / CVE-2026-123007: our take after reading the Xint and Wiz writeups
Two teams independently built working unauthenticated RCE exploits against nginx. F5 confirms the bugs, and fixes are out (1.31.9 / 1.30.7). This is a serious one. Patch.
But the version number alone doesn't tell you whether a server is exposed.
The widely quoted "98.9% of nginx hosts are in the affected range" counts version strings. The two critical bugs (CVE-2026-123007, CVE-2026-123633) sit in the HTTP/2 code. They can only be reached if HTTP/2 is enabled, and nginx doesn't enable it by default.
A server is exposed to them when all of this is true:
- nginx 1.9.5 to 1.31.8 (stable branch: up to 1.30.6), without a vendor backport
- HTTP/2 module compiled in (true for most distro packages)
- HTTP/2 enabled on a listener an attacker can reach
Check from outside:
curl -sI --http2 -o /dev/null -w '%{http_version}\n' https://HOST/
"2" means HTTP/2 is on, "1.1" means it's off. Test the nginx itself, not a CDN in front of it.
Check on the server:
nginx -v
nginx -V 2>&1 | grep -o with-http_v2_module
nginx -T 2>/dev/null | grep -E 'listen.*http2|http2 +on'
No output from the last command means HTTP/2 is not enabled.
How common is HTTP/2 on nginx? We spot-checked a few hundred nginx HTTPS endpoints listed on Shodan: roughly two thirds negotiate it. So not 99%, but still millions of servers.
What to do:
- Update to 1.31.9 / 1.30.7 or your distro's fixed package. Distros backport, so check the advisory, not just nginx -v.
- Can't patch yet? Turn HTTP/2 off until you can.
- The same release fixes three more RCE bugs that need other features (resolver with a variable proxy_pass, HTTP/3, mail proxy). Patching covers those too.
Xint: nginx2root.com/
Wiz: wiz.io/blog/nginx-http2-rce-…
F5: my.f5.com/manage/s/article/K…



































