Alex Haydock

@alexhaydock@infosec.exchange
815 Followers
1.9K Following
377 Posts

Security Engineer. Dismantler of Torment Nexuses. Friend of Blåhaj. Knows too much about IPv6.

Interested in understanding how complex systems fail. Frequently interested in understanding how to make them fail.

Currently helping build Tor & DNS infrastructure with @EmeraldOnion.

   

Pronounshe/him
Localeen_GB
Bloghttps://blog.infected.systems
GitHubhttps://github.com/alexhaydock

Dear #tooters,

Don't ever stop posting your nerdy passion projects.

Even when I can't understand 90% of what you're saying, I love them, and they bring way more healing to a very hurting world than you might surmise.

shoutouts if you have better computer specs than this bus
Mastodon #infosec , I am trying to maintain a list of threat intel platforms that have passive DNS, historical whois, malware analysis, threat databases here https://gist.github.com/Te-k/2a5a1885249cfd07f417b47d291c4b98
Am I missing any important platform in that list?
Threat Intelligence platforms

Threat Intelligence platforms. GitHub Gist: instantly share code, notes, and snippets.

Gist
If anyone is planning on heading to BSides Birmingham today, I’ll be giving a talk with some colleagues later on Threat Layering in MITRE Navigator, as well as some of the fun benefits we can get from Detection as Code 

Sometimes a disk image just strikes you not because it's got some weird layout or elaborate copy protection, but just because it *looks cool*.

The data on this game, Eye of Horus, forms some very regular patterns.

@kunai_project, the better-than-sysmon Linux eBPF logging tool, now has a sandbox for running samples! https://github.com/kunai-project/sandbox

And there's even a handy web UI!

https://github.com/kunai-project/sandbox-ui

GitHub - kunai-project/sandbox: Sandbox samples and monitor them with kunai

Sandbox samples and monitor them with kunai. Contribute to kunai-project/sandbox development by creating an account on GitHub.

GitHub
Four years ago we introduced this #curl graph

12+ hours in and this is still getting boosts and likes so I thought I'd follow up with some of the graphs from the past 12h.

The Wii has handled this far better than I expected, honestly.

We've settled in to an average rate of approx 10 requests-per-second, down from a peak of 40. Almost all responses are taking less than 0.1 seconds now, though the heatmap suggests it was struggling a bit more when we were up at 40 per-second.

Ah this might explain some things.

The Wii is coping very well so far with a fairly consistent load of around 20-25 requests per second.

I'm shocked that the load averages are as low as they are, though the page responses are definitely slower than they could be so we might be bottlenecking elsewhere.

Uh oh... here we go