
#Hetty: #OpenSource #HTTP toolkit for security research
https://www.helpnetsecurity.com/2025/03/10/hetty-open-source-http-toolkit-security-research/

#Hetty: #OpenSource #HTTP toolkit for security research
https://www.helpnetsecurity.com/2025/03/10/hetty-open-source-http-toolkit-security-research/
Alright, Go developers, listen up!
So, for goodness sake, pay super close attention to the names of your modules! One little typo and bam! You've got yourself a nasty infection. As a pentester, I see this kind of thing all the time, sadly. Tiny mistakes, HUGE consequences. This malware then installs a backdoor. Totally not cool, right?
Therefore, check your imports, folks! And make sure you're getting your devs trained up on security. Automated scans? Nice to have, sure, but they're absolutely no substitute for a manual pentest! What are your go-to tools for fighting this kind of attack? Oh, and yeah, IT security *has* to be in the budget, that's just the way it is.
Our latest paper is on Arxiv: ARACNE: An LLM-Based Autonomous Shell Pentesting Agent
Hey everyone, what's cooking in the open-source universe?
So, there's this Python library pretending to be a music tool (automslc), but get this – it's actually illegally downloading songs from Deezer! And the worst part? It turns your computer into an accomplice in a huge music piracy operation. Seriously, a digital pirate cove.
And then there's this npm saga with @ton-wallet/create... Crypto wallet emptied, just like that!
The moral of the story? Open source rocks, but blindly trusting everything is a recipe for disaster. Always double-check those dependencies! Automated scans are cool, but a real penetration test? That's pure gold.
Clients are always so appreciative when we can spot and fix this kind of stuff beforehand!
Now, I'm curious: What are your go-to methods for keeping your codebase squeaky clean and secure? Any tips or tricks you'd like to share?
Hackers Call Current #AI Security Testing 'Bullshit'
https://it.slashdot.org/story/25/02/11/191240/hackers-call-current-ai-security-testing-bullshit
True Story, bruh:
Back in the 90's people would go on about how superior emacs is as an editor. And some cheerleaders would hound me about why I "still" used (and still do today) vi... vim actually. Even for doing things like Usenet news, and the email client. Joe was in a lot of email readers, which is pretty much slobberproof, BUT...
My answer was and still is simple. I hack and break things for a living. I've never seen emacs installed on a bridge, router, or frankly any other network device. Hell, when the web came around, emacs was only rarely on those servers, either. But ed and vi is (was?) on pretty much all of them.
So that's what I learned. And my personal ecosystem and workflow is all about vi(m) and nothing about emacs.
Even though I'm a Lisp cheerleader, lol.
Do I hate emacs? No, but I do very much dislike the overpowering smell of religion that seems permeate it's very existence, like those dirty air lines fuming from the Peanuts character Pigpen.
Some call me a space cowboy. Some call me a gangsta of #Lisp
Also why am I pentesting today?!
I should have never looked for this in the first place.
It was because my mom was watching The Price is Right and I got bored but still wanted to be next to my mom and I got a hunch and pulled out my laptop and sat next to my mom while she watched Drew Carey and we just parallel played for a bit and then I found it!!!! And I told my mom about it! She said "That's nice dear but I'm watching my shows" and I think that technically violated my NDAs but she wasn't really listening so a tree in the forest and all of that. Anyhoo.... not sure what to do with this finding...
Soooooo I found a massive vulnerability today, the day before Thanksgiving.
Buuuuuuut it's looks like its existed for a couple of years.
So, should I report it RIGHT NOW!!!! The day before thanksgiving? Or wait until next week.
On one hand, they'll have to react to it as its huge. And it could interrupt their time with family and a major holiday.
On the other hand, it's been around for so long, what's another couple of days going to change anything?
On the third hand, if this gets exploited over the holiday weekend, it's on me and could affect even more people.
Hmmmmmmm.... choices choices.
Wireless Penetration Testing Tools
https://meetups.infosec.exchange/events/eff4ac94-c888-4cb6-8276-6c1caa196bf5
I’ll stick with my Devious Decoder Card (from @deviantollam) but this is still cool and better than nothing, something else to try besides taking a picture of the key and trying to decode with a line/depth overlay.
Kwikset as shown in the video is pretty easy to almost sight read anyway but I wonder if the Flipper app would be harder to use with finer depth increments like Schlage or Best SFIC.
Still cool to think they could add many more key depths over time though.
https://www.youtube.com/watch?v=RPrd-S5Cmxo #FlipperZero #locksport #locksmith #keys #pentesting
Open-source Packet Sniffers
El lado del mal - Cómo crear un volcado de procesos en GNU/Linux y buscar "leaks" de información https://elladodelmal.com/2024/09/como-crear-un-volcado-de-procesos-en.html #Linux #Forensics #KaliLinux #pentest #pentesting
Just finished up another fun SE/physical onsite pentest.
Physical security at this location was TIGHT. Some of the best I've ever seen. iClass SEOS with Elite Keys; downgrade disabled, Mantrap-style turnstiles with reverse-tailgate detection, ADA doors require manual unlock from security (Is that even legal?
ESPKey was basically my only shot at a technical/physical bypass. I couldn't get them to agree to let me try it, but I honestly wouldn't be surprised if they were actually using OSDP.
So I showed up carrying a cardboard box and security just buzzed me in.
FXBG Hackers - 0x1A - Oct 2nd 2024 @ 7pm
October 2, 2024, 7:00:00 PM EDT - GMT-4 - Red Dragon Bewery, 22401, Fredericksburg, United States
https://meetups.infosec.exchange/events/95baa898-87c5-417f-a170-1c72a1e03af1
10 Ways To Detect Phishing Emails