RE: https://infosec.exchange/@ministraitor/115420393928205564

Curious about a developer’s vibe-coding journey? @iglocska is sharing his experiments and insights at hack.lu 2025!

#vibecoding #ai #cybersecurity #hacklu

The CHAOSScon CFP is OPEN! 🎤

Share your knowledge on open source project health metrics and tools with the community in Brussels, Belgium, on Jan 29, 2026.

Don't miss out! Submit your talk:
https://forms.gle/5xuXDLYgYzrCYkWb9

#CHAOSScon #CFP #OpenSource #Brussels

Seeing a presentation of the Kaitai project.

If you need to document or describe or decode binary format, Kaitai is clearly there to help.

https://kaitai.io/ @kaitai

#hacklu #kaitai #dfir #cybersecurity

@joel @lcheylus True it's country level at the current stage.

Meet Plum, The Challenge Of Your Own ASR For Free - Paul Jung
https://youtu.be/a8hMZ3T4nTc
#HackLu

@adulau this was a fun read https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell

Next up at #hacklu2025 is Paul Rascagneres with a talk about threat actors that use blockchains. Taking us through what smart contracts to get to the malware and exploitation

Smart contracts can directly store malware!

And he’s on Mastodon as @r00tbsd ! Give him a follow.

Exploring Threats Leveraging Blockchains by @r00tbsd at #hacklu
working at @volexity

Thanks to @xme for the picture.

#conference #hacklu #blockchain #cybersecurity

Following a discussion with @ddu about a cybersecurity format that uses YAML, I’ve come to the conclusion that the acronym really stands for “Yet Another Misaligned Language.

#yaml #cybersecurity #hacklu

All details for the iOS analysis using the Sysdiagnose analysis framework workshop - advanced session workshop details are available on the discourse:

https://discourse.ossbase.org/t/ios-analysis-using-the-sysdiagnose-analysis-framework-workshop-advanced-session-david-durvaux-christophe-vandeplas/674

#hacklu #conference #cybersecurity #mobileforensic #dfir #forensic

Thanks to @ddu and @cvandeplas

@mumblegrepper

Indeed, we usually see two different kinds of groups:

• Highly competitive teams, focused on winning and willing to do whatever it takes to be first.

• Highly cooperative teams, eager to improve their skills and share their knowledge.

In my experience, the second kind actually uses AI just as a tool compared to the others just as a shortcut to grab a flag. ;-)

#ctf

@sergedroz @hack_lu @cryptax @ddu @firstdotorg

@hack_lu @adulau @ddu @firstdotorg by the way, I didn't mean to say there was any easy solution, or that I have "the" solution. It's just that there's an issue, and we'll have to try and tackle it.

Just discovered a new RAT at #hacklu and it seems the name can confuse a lot of french-speaking persons.

RATatouille

Not sure it''s a good idea for the SEO of the RAT author. ;-)

🔗 https://www.aikido.dev/blog/catching-a-rat-remote-access-trojian-rand-user-agent-supply-chain-compromise

#rat #cybersecurity

Welcome to the **hack.lu 2025 Conference Challenges**!

During the hack.lu 2025 conference, a series of challenges will be running — register and play!

Registration code: `hacklu`

🔗 https://hacklu.firstseclounge.org/

#ctf #challenge #hacklu #cybersecurity #challenges #infosec

Thanks to @ddu and the whole team for the hard work.

During the Call for Failures at #hacklu on Wednesday, 22 October, I’ll be presenting:

“The cve-search design failure(s)”

Yep, the things I got wrong, the kind you only truly notice once you start implementing them.

#cybersecurity #failure #fail #conference #opensource

An interesting lighting talk at #hacklu presenting a tool for Offline decryption of SCCM database secrets.

https://github.com/MartinoTommasini/offlineSCCMdecrypt

#sccm #decrypt #cybersecurity

@cryptax "AI is an issue to CTFs. When I say so, some people immediately argue “it’s a tool”. Yes, yes, it is! I do like AI for plenty of things, but nevertheless, in my opinion, it’s going to kill the sould of CTFs if we don’t work out for new solutions, new challenges etc. I’ll blog on that one day."

Thanks for sharing.

@adulau and @ddu discussed similar issues with the recent CTF designed for @firstdotorg

We are very curious to read your blog post.

Over my career and as part of personal projects I have repeatedly scanned nearly all of the Internet's routable IPv4 space and some portion of IPv6 space. In one of those projects we were scanning multiple times a week. If you've never been in this space I can assure you that the amount of unpatched gear and software would surprise you. The amount of gear that is YEARS past EOL is substantial. The amount of services that should never be public facing is, to be blunt, inexcusable. Even after the publication of the ETERNALBLUE exploits and the WannaCry, NotPetya, and related worms it still took months to see any significant reduction in exposed SMB endpoints. Even then, IIRC, a significant % of that reduction was due to ISP action and not system owners clueing up. There are often reports of massive DDoS events sourced from compromised routers, cameras, DVRs, cable models, etc. The original Mirai botnet is an excellent example of how impactful a worm infecting cameras and routers just using default creds can be.

It is my personal opinion that in every international jurisdiction it should be both legal and protected from civil repercussions to wipe all data and render permanently inoperable(1) any device or service directly connected to the Internet and remotely accessible with a default (out of the box or in documentation) credential or has a publicly disclosed vulnerability older than 2(2) years old which enables the action.

1. This doesn't include setting the device on fire, creating an explosion, etc. If it merely drops internet or power then I suspect someone's lawyers will have something to say to the party responsible for such a negligent implementation or management.
2. Arbitrarily selected to allow controlled patch time, detection of oversight, etc. We could even start with something like 4 years and decrease the window over time. We could give folks a 1 year warning to get their house in order.

I believe that the initial result would be chaos but soon after the internet would be a "safer" place . I also think that perhaps there would be more pressure on vendors to improve the security of the device or service as well streamline and user proof the patching and hardening process.

For those who might be concerned that their gear, software, network, or services might be impacted I say:

Quit shitting up the internet for everyone!

#Security #Opinion

I've spent some time on hack.lu this weekend. Here's the solution for Crypto / MÄNUAL that gave me the flag:

https://pastebin.com/W9De4qDK

#ctf cybersecurity #hacklu #fluxxfingers @hack_lu

hack.lu 2025 playlist

#playlist #hacklu #cybersecurity #music

🔗 https://2025.hack.lu/playlist/