I'm bored and stuck in an Orlando airport for an indeterminate amount of time, tell me why!

Any clever minds have a theory?

( Warning not fluent english )

Hello evryone, I want to make this by myself because it can be hard to learn ethical hacking without getting mogged censored by gpt or claude. Plus the models online and this project don't garantee your safety

I don't have another pc offline dedicated to hacking to run thoose models and transfer some personal files to a Vm doesn't garantee you 100% Safety

So any tips guys ?

Hi, I'm the developer.

I have worked in network security for almost 15 years. I got annoyed with Fing and other network tools that charge close to $100 a year, or let you scan only a few times a day. So I built my own from what I know from work.

I wanted the feeling of Kali Linux in my hand, but only for defense: point my phone at my own network and see what is really there. No attacks, no password guessing, nobody's traffic read. That became Netglow.

The hard part: knowing what each device really is

Android 10 and up hides other devices' hardware addresses, so most scanners just show "Unknown". That is where most of the time went:

• Dozens of protocol specs, vendor docs and firmware sources, read line by line.

• Down to the low level microchips inside smart plugs, bulbs and DIY boards, like the ESP family, because each chip gives itself away in its own small way.

• Camera makers each answer on the network in their own way, and Netglow knows many of them.

• Over 40,000 hardware maker prefixes and a catalogue of over 23,000 phone and tablet models.

• Thousands of lines of research notes, every finding checked before it went into the app.

Why it is free

I have a lot of knowledge from my work, and I decided to give it away: high quality apps, deeply researched and checked again and again, data safety first and privacy to the max. No ads, no bullshit. People deserve good quality and privacy, for free.

If you want to support me, you can, but it is fully optional.

What it does, free, unlimited scans

• Who is on my Wi-Fi. Every device with its name, maker and model when it says them. Rename a device and it keeps your name even on a new address.

• Is my hotel room or rental OK. It lists devices on the Wi-Fi that answer as a camera or stream video, and says why each one was flagged. It also looks for camera hotspots nearby. It tells you plainly what it cannot see (a camera that only records to a card or uses mobile data), so it is one check among others, not a guarantee.

• Security check for your home network. A score with a plain fix for each risk: risky open ports, what your router opened to the internet, how your Wi-Fi is locked, look alikes of your network nearby, whether your DNS answers are honest and whether someone reads your secure connections in the middle.

• Tools. Ping, traceroute, port check, DNS lookup, Wake on LAN, a live signal meter and channel advice.

Private by design. No ads, no bullshit, no tracking, no analytics, no metrics, no account. Nothing it finds leaves your phone, and there is no server of mine.

Pro is that optional support, one payment, no subscription, and it adds: a Bluetooth radar that warns about a tracker moving with you, checks for devices that let anyone in with no password, spoof watch, known flaws for your devices, a PDF report and a background watch of who joins your Wi-Fi.

Honest note: the code is partly AI generated and I had help with this text.

Play Store: https://play.google.com/store/apps/details?id=com.zanoshky.netglow

Guide: https://zanoshky.github.io/netglow-app

I would love to hear what it finds, or misses, on your network.

The Bose S1 pro battery, in theory, is there any fun ways I could convert it to a power bank or something else maybe? Power LED’s? Let me know ideas and how do I hook to its port?

Another easy TryHackMe Security challenge solved. One of hundreds to come.

Feel free to review my solution for this one.

https://hackingknack.com/blog/writeups/challenges/tryhackme/5-minute-hacks/try-hack-me-5-minute-hacks-corridor/

Hello, I am kinda new to cysec and I have been looking around and it seems to me that everyone is kinda slowly doing more and more hardware so I wonder, would It be advisable to skip hackthebox and CTFs completely and startover learning electrical and hardware eng?

Apparently Strike 3 is able do identify user from dowloaded content....anyone know how their embedding a callback in a video file?

https://www.latimes.com/business/story/2023-12-12/column-this-porn-company-makes-millions-by-shaming-porn-consumers

I'm studying for the OSCP and have already taken the PNPT and eJPT, for context. I'm redoing notes on Linux privilege escalation, and getting stuck on hunting creds, so looking for advice on how to do it more efficiently.

Currently the main methods I see are searching for the word "password" everywhere in specific ways and grepping configs for the keyword.

The main problem is every which way I try to search, the command outputs hundreds to thousands of lines and entries for "password" on every host. It's just way too much to search through, and I feel like there's a better way. Got any tips for this area?

The French government has said that Shahid Kaveh, an Iranian hacking group, was behind a cyberattack on refrigerators that ruined food at some 700 food outlets in October. The group is also known under various other names and has been accused of similar attacks in the past. Iran's Foreign Ministry called the French allegations "baseless and hostile."

While working on my Master’s thesis benchmarking WPA3-SAE timing side-channels, I ran into a limitation on the ESP32 esp_wifi_80211_tx() allows raw frame injection, but Espressif’s closed-source wifi blob "libnet80211.a" artificially blocks Auth, Assoc, Deauth, and Disassoc subtypes.

Inside libnet80211.a, ieee80211_raw_frame_sanity_check drops these frames with wifi:unsupport frame type. Here is how to bypass it on recent ESP-IDF versions (IDF v6.x).

Why standard tricks fail on modern ESP-IDF

Same name function override. On older IDF versions, ieee80211_raw_frame_sanity_check was a weak symbol (W). On modern IDF versions, it’s a strong symbol (T), causing ld: multiple definition errors.

\--wrap linker flag: Fails silently. The call from esp_wifi_80211_tx to ieee80211_raw_frame_sanity_check is an intra-object branch inside ieee80211_output.o. Linker --wrap only rewrites undefined external references, so it misses this call entirely.

By Overwriting instructions directly in the .o breaks Xtensa linker relaxation passes (dangerous relocation errors).

U can simply fix this via Symbol Weakening via objcopy

We can use xtensa-esp32-elf-objcopy to convert the strong symbol inside the binary archive into a weak one:

xtensa-esp32-elf-objcopy \\

\--weaken-symbol=ieee80211_raw_frame_sanity_check \\

components/esp_wifi/lib/esp32/libnet80211.a

and now u just define your own strong implementation inside your application C code:

int ieee80211_raw_frame_sanity_check(int32_t a, int32_t b, int32_t c) {

return 0; // which skips the security check lol

}

Because strong symbols override weak symbols globally during linking, all callsincluding internal calls within libnet80211.a rebind to your function.

Verification

Serial Logs show: wifi unsupport frame type errors completely disappeared.

Tshark confirmed capture of 802.11 Authentication frames (Subtype 11, Algorithm 3 - SAE) injected directly from the ESP32s.

Injecting a valid SAE Commit (P-256 scalar + element) caused hostapd on the target AP to process the request and reply with its own SAE Commit (this is a documented DoS vector attack against WPA3)

TL;DR: Run objcopy --weaken-symbol=ieee80211_raw_frame_sanity_check on libnet80211.a, define int ieee80211_raw_frame_sanity_check(...) { return 0; } in your app code, and esp_wifi_80211_tx() will allow any frame subtype.

Note that all control 80211 frames are also injectable after the patch.

For more details :

https://github.com/mahdamin/esp-idf-injection-ng

I've recently updated Silverseal after my talk in Nullcon and can finally release the ARM64 version of it - making it the first bootkit targeting Linux distros on ARM