Andy Swift retweeted
Spotify: open.spotify.com/show/3PeV2F…
Apple Podcasts: podcasts.apple.com/us/podcas…
Amazon Music: music.amazon.com/podcasts/cf…
YouTube: youtube.com/channel/UC5L2Q76…
Andy Swift retweeted
Episode 48: Citrix, Cloudflare, and Credential Chaos!
@0xTib3rius & @SwiftSecur1 chat about a bunch of small topics, from Citrix bugs, to passkeys, to whether Cloudflare is actually just a huge MiTM attack.
Links below!
Andy Swift retweeted
Hello, Little People Living Inside Of My Computer,
I have made my second ever YouTube video briefly discussing the Chinese government trying to compromise companies in Malaysia.
It was fun.
youtu.be/ZcsVsr4rpgs
Andy Swift retweeted
Have seen some posts on this that contain an (understandable) misunderstanding of probability.
If you use an RNG (true or pseudo), the chance of generating any number is the same as the chance of generating any other.
If you ask for 2 6-digit random numbers and you get 123456 and 000000, your RNG isn't necessarily broken.
As humans, we see patterns in everything. But patterns can occur by chance. The chances of generating 123123 and 111111 and 428946 are exactly the same.
In fact, if an RNG never generated "pattern" numbers, it would actually be less secure than one that did.
Even the quoted post is wrong when it says "Each key should be a 116-digit number, but one was just 4."
Technically, the key that was "just 4" was a 384 bit number with 381 preceding zeroes.
Many keys, when randomly generated, will have preceding zeroes. Many will have preceding ones.
The "value" of the key is 4. The length of the key is still 384 bits. The value isn't what gives the key its strength. The key of value 2^384 - 1 isn't the strongest key, for example.
However, that doesn't mean a key of value 4 isn't insecure, but it's for a very human reason.
When we brute force keys, we need a starting point. While we could theoretically choose any number, we tend to just go with what is easier: starting from 0.
So yes, you'd brute force one of these keys on the 5th attempt, and the others would fall soon after.
But if you started from the other end of the key space, from 2^384 - 1 and decremented instead of incremented, you might also find a key on the 5th attempt.
That would still be bad.
You could choose an arbitrary starting point, and get lucky. That would also be bad.
All said, that doesn't mean the key generation process they used was good. The fact it produced a bunch of easily brute-forceable keys is very, very, bad.
Andy Swift retweeted
Episode 47 - Cars, Cats, and Clankers with dawgyg!
@0xTib3rius & @SwiftSecur1 are joined by Tommy DeVoss (@thedawgyg) to talk about his cars, his cats, and his AI hacking.
Links below!
Andy Swift retweeted
Crawlers are a normal part of the web. Yandex runs a search engine; of course it generates bot traffic.
Bot traffic from Russia does not automatically mean Russian propaganda bots. Yet people here, including journalists, keep treating the two as interchangeable.
That Cloudflare chart shows automated web requests from Yandex’s network. Where’s the data showing that propaganda accounts stopped posting?
Journalists in particular need to understand this distinction. Precision matters when a misread traffic graph becomes the basis for a political narrative.
Andy Swift retweeted
#30 - I Read The Policies So You Don't Have To;
Reddit (Social Media Discussion Platform)
medium.com/@ItsNotNicole/i-r…
Andy Swift retweeted
Exploiting Reversing (ER) Series | Article 10: iOS Security Research (part 01)
223 pages, free. The first article in the series aimed at iOS itself, and the opening of a multi-part sequence.
Published on:
blackstormsecurity.com/resea…
This article will be published on exploitreversing.com/ next week.
I would like to thank Ilfak Guilfanov (@ilfak) and Hex-Rays SA (@HexRaysSA) for the continuous support.
Hope you enjoy the read!
#iOS #Apple #VulnerabilityResearch #ExploitDevelopment #ReverseEngineering
Andy Swift retweeted
Episode 46 - HackKorman is BackKorman!
@0xTib3rius & @SwiftSecur1 are joined again by @ZackKorman (the HackKorman) to talk about AI agent security, or lack thereof.
Links below!
Andy Swift retweeted
Today is the second ticket release for #BSidesLDN2026
The release will be at 1337hrs!
Please read out Ticket FAQs for full details: bsides.london/ticketsfaqs
#BSides #London #Tickets
Andy Swift retweeted
My colleague @mgreen27 published velociraptor-skills, a set of reusable AI skills for DFIR with Velociraptor.
These skills guide artifact selection, collection, hunting, analysis, and context management. They use a shared Python harness, vraptor, through a command-line interface rather than an MCP server or individual AI tools. The goal of using a separate harness is to optimize token use, control performance, and standardize the format of generated analysis notes.
Read the full blog post here: labs.infoguard.ch/posts/ai_a…
Andy Swift retweeted
The #BSidesLDN2026 CFP closes TONIGHT at midnight! ⏰
There’s still time to get your submission in.
🎤 Call for Papers
🐻 Call for Rookies
🛠️ Call for Workshops
No REST ’til Hammersmith! 🎸
bsides.london/cfp2026
#Security #BSides #London #CFP
Andy Swift retweeted
Microsoft issued only 1 single notice about the passkeys rollout prior to it starting in September.
Someone fact check this. Is this correct @merill
mc.merill.net/message/MC1426…
Andy Swift retweeted
Spotify: open.spotify.com/show/3PeV2F…
Apple Podcasts: podcasts.apple.com/us/podcas…
Amazon Music: music.amazon.com/podcasts/cf…
YouTube: youtube.com/channel/UC5L2Q76…
Andy Swift retweeted
Episode 45: AI & Bug Bounties with Casey John Ellis!
@0xTib3rius & @SwiftSecur1 are joined by @caseyjohnellis to talk about bug bounty (and other things) in the era of AI.
Links below!
Andy Swift retweeted
I’m doing a live podcast on LinkedIn of all places in about 30 minutes. Going to say mean things about the doomers.
Go find me on that site if you want to watch.
Andy Swift retweeted
I got you fam
Andy Swift retweeted
n8n just got a CVSS 10.0 public exploit.
CVE-2026-21858 (“Ni8mare”):
unauthenticated file read → full RCE. Working PoC is circulating.
Any internet-facing n8n that missed the patch is one request away from compromise.
github.com/Chocapikk/CVE-202…
#Cybersecurity #AI #AISecurity #MCP #Claude #GPT #Infosec #Trending #RCE #AppSec































