@freddy Not sure I'll be able to have the original trigger now that a media proxy got introduced (don't know if it works retroactively).

But I have an idea for a repro, adding then deleting an <img> to the document. I guess what makes debugging this difficult is that you need a point-in-time document snapshot to see the true source. Even seeing the <img> may not be meaningful without e.g. it's surrounding <div> with the post content.

It seems that Avast managed to settle the lawsuits related to their data abuse in both US and UK. While in the former they agreed to pay a fairly moderate fine, UK let them off the hook even easier. They are offering two years of free software to eligible UK users which is, quite frankly, a joke. It costs Avast exactly nothing, it allows them to email past users on a legal basis and gives them a chance to win them back. Really, who agreed to that?

#Avast #Jumpshot #privacy

Interesting Git repos of the week:

Strategy:

* https://github.com/SoShinySoChrome/human-incident-response-framework - tackling the human side of IR

Threats:

* https://github.com/Mickinthemiddle/CLOAK - deception techniques used by operators

Detection:

* https://github.com/Chick3nHawk01/Open_Source-CTI-Tooling - open source CTI tooling

Bugs:

* https://github.com/suce0155/CVE-2026-32996 - a backup route for LPE

Exploitation:

* https://github.com/cloudflare/security-audit-skill - more skills for your 🤖
* https://github.com/almounah/silph - another tool to steal your memories
* https://github.com/TheZeroSlave/WPE - like Burp but for non-HTTP Windows traffic (HT @Ichinin for the reminder)
* https://github.com/interference-security/echomirage - if you remember shade/DOA... someone has saved a copy of Echo Mirage, another Windows MITM testing tool
* https://github.com/Mafifrizi/ARES - someone has been going through adding my AD attacks (credited nicely :)) on Linux to its repertoire
* https://github.com/IoTS-P/Akiba - batch processing Ghidra
* https://github.com/vulncheck-oss/initial-access-community - some nice ideas on initial access from @albinolobster and friends

Hard hacks:

* https://github.com/GlasgowEmbedded/glasgow - it's always nice in Glasgow with @whitequark
* https://github.com/xiaobor123/vuls-find-VxWorks - VxWorks until it doesn't
* https://github.com/xiaobor123/vul-finds - more cute bugs

Data:

* https://github.com/cisco-ai-defense/aibom - AI usage needs to be transparent... and if not, well, some of us will be looking for it in any event 🤖

Cryptography:

* https://github.com/nationwide-group-oss/cryptoptic - time to start taking PQC seriously

Development:

* https://github.com/ItzLevvie/dind - HT to @GossiTheDog for pointing it out, but run Windows inside of GitHub

Nerd:

* https://github.com/sure-fire/derbypi - some neat extensions for Pis from @surefire

#security, #research, #code

Introducing 𝙷𝚊𝚠𝚔𝚃𝚞𝚊𝚑𝙱𝚛𝚘𝚠𝚜𝚎𝚛.𝚎𝚡𝚎

- 15 KB native web browser
- 6 MB of RAM for the host
- 0 lines of Visual Basic (no C# cuz idk how to write it)
- no URL bar because surfing through 88x31s is more fun
- title bar kept cuz then u can close it and minimize buttons

@freddy Interesting theory! I do blackhole some sites but I doubt any URL of those would point to :3000...

@freddy This is what I believe a native FF log message resulting from an attempt to load from localhost:

"Local Network Access permission required: top-level site “https://infosec.place/”, initiator “https://infosec.place/”, attempting to access target “http://localhost:3000/assets/images/og-card.png” (127.0.0.1:3000) via http. Secure context: True"

I could reproduce it by scrolling a shit ton in my timeline (won't do again), but I think a minimal test case would be a simple `img src="http://localhost...` served from a non-local origin.

In that case though the source would be there in Inspector, but in case of Akkoma infinite scroll does some magic that prevents me from simply looking up the tag by URL, that's why I'm thinking if some kind of "stack trace" is available for network events that would lead me to the offending element?

@TarkabarkaHolgy Blood Knights is 100% wh40k compatible too!

"If it only were that simple." - George Washington

@securestep9 It looks client-side so you could get the same info from dev tools no?

#Windows experts, can you answer this without trying:

How many times do you need to press the down arrow to select C:\Users\Public?

#UX #UI

Session timeouts[1] provide great examples of #compliance disconnects from reality:

When booking for events it *always* takes *days* to get from registering for an event and getting there to show your QR or whatever. And while an attacker who hijacks your session has 0 benefit from accessing it for a prolonged time, somehow #security finds it crucial that users are auto logged-out after 30mins.

It would take just a *tiny* bit of thinking to avoid making things worse for everyone.

[1] https://wstg.owasp.org/latest/4-Web_Application_Security_Testing/06-Session_Management/07-Session_Timeout/ (congrats to #OWASP for breaking all your indexed links in search engines, also very helpful!)

Re: this one I'm still curious how I could tell which document node triggered a network event (denied, with an img Initiator) I see in dev tools. I can't find the corresponding URL by searching in Inspector, DeepSeek hallucinates all the solutions, maybe @freddy has a tip?

#Firefox

RE: https://infosec.place/objects/c55e1bcb-86a9-4d16-b9fb-83dccaeb4dad

#BOFH excuse #442:

Trojan horse ran out of hay

@jerry You are the Man, thanks! @dey

@jerry @dey I count HTML as code...

The Degraded Search Engine

Bonus speedpaint: https://www.peppercarrot.com/en/miniFantasyTheater/071.html#bonus

#webcomic #krita #miniFantasyTheater

@jerry @dey I can see the Initiator is an img, but I can't find anything seemingly related in inspector + network rectord don't tell me what code initiated a request. That's the status.

@dey @jerry But I'm not using Mastodon, this is an Akkoma instance. And this only happens if I scroll back to the point in my timeline when I first got this notif. It'd be really weird if this behavior didn't trigger at around page load.

@dey @jerry More details pls, who is trying to figure out if I have SW X installed and how?

@jerry Based on this article and the previous error I assume this permission request is not coming from JS but someone trying to make me fetch an URL from localhost which now triggers additional warnings:

https://support.mozilla.org/en-US/kb/control-personal-device-local-network-permissions-firefox

At this point I'm not sure if it should be illegal for posts to contain references to localhost.