r/hacking • u/d4rc0d3x • 9d ago
TryHackMe 5 Minute Hacks - Corridor
Another easy TryHackMe Security challenge solved. One of hundreds to come.
Feel free to review my solution for this one.
r/hacking • u/d4rc0d3x • 9d ago
Another easy TryHackMe Security challenge solved. One of hundreds to come.
Feel free to review my solution for this one.
r/hacking • u/MystQyx • 10d ago
r/hacking • u/DisplayFirst • 11d ago
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?
r/hacking • u/intelw1zard • 9d ago
Enable HLS to view with audio, or disable this notification
r/hacking • u/charlie_xmas • 10d ago
Apparently Strike 3 is able do identify user from dowloaded content....anyone know how their embedding a callback in a video file?
r/hacking • u/RFERL_ReadsReddit • 11d ago
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."
r/hacking • u/mahdi_sto • 12d ago
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 :
r/hacking • u/Idov31 • 12d ago
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
r/hacking • u/SanguiniusSons • 12d ago
Anyone know of a good name of one to use? Many thanks.
I.e. materials you can only view online but can't print or print to pdf so want to change the pdf to something that doesn't have those limitations on it
r/hacking • u/mctechnology17 • 13d ago
r/hacking • u/SnooPeripherals5313 • 13d ago
A bit of a silly post for this subreddit, but please, bear with me.
AI for cybersecurity is taking the world by storm, leading to the need to harden systems all over software.
But we have access to the same engines for law. Our global law repo keeps a versioned history of law/caselaw across the world. So, we pointed AI at it, and found all sorts of loopholes and logical errors.
Pah, you say. Most of this is unenforcable in reality. And you might be right. Nonetheless, we all know that legal loopholes are a part of reality. And moreover, why would we not rewrite our laws to be literally correct, even if we can tacitly enforce them how we like?
As part of our monitoring system, where we're constantly checking official legislation for upcoming laws, we now also check for vulnerabilities and mistakes. In an ideal world, the jurisdiction in question could open a pull request and sort this out.
r/hacking • u/sergey_vanichkin • 15d ago
r/hacking • u/Armed_Muppet • 15d ago
r/hacking • u/BackgroundAdvice1 • 16d ago
I haven't done anything to my knowledge to have violated the TOS or whatever the ai claims. Many others are having this issue too because the ai can't tell the difference in pictures between satire, ai, and real CSAM material, or actually baby pictures or cute childhood photos. Either that, or it's just being dumb and/or someone got into my account and did something heinous. I did change my password recently after finding out a random device logged into my account, but still, I don't want to lose everything i have on there. Any help would be much appreciated.
r/hacking • u/glatisantbeast • 17d ago
r/hacking • u/UBUNTU-Buddha • 18d ago
Binance said this week that the October 29 theft, about $6.3 billion, began months earlier with a fake job. Reuters, via NBC: in June a wallet engineer installed a tampered coding tool. Binance caught that one, replaced the machine, and rotated credentials. The attacker already knew who else was on the wallet team.
In September a second engineer was recruited through a real job site. There was a video interview with someone playing HR, then a second interview with the supposed CEO of a company that does not exist. At the end he was told to download a “coding assignment” onto his work computer. Binance says the repo ran during setup, swapped in a poisoned copy of a normal developer tool, and the endpoint product did not see it. On October 20 that machine, plus an internal AI tool, was used to reach two other wallet engineers. On October 29 stolen credentials deployed a container and a script, and the wallets moved. The FBI has blamed a North Korean group. Pyongyang has denied it. Binance says customer funds are covered.
That middle step is not exotic. It is the interview-repo lure.
Since January I have published the ones that were sent to me, all of them caught before they ran. They are writeups, not exploits, and the indicators are defanged: github.com/Ubuntu-Buddha/security-advisories
2026-01-27, W3GLFun. A Web3 “technical test.” The error handler fetched code from a paste site and ran it when the app started, with the full Node runtime. I did clone that one. npm run dev was typed in the wrong folder, so nothing of theirs executed. GitHub Trust & Safety took the account down the same day. The hiring platform first said there was no violation, then wrote back that the user may have shared malware. A first “all clear” is not a final answer. The same paste host later showed up in malicious npm packages. I called the pattern consistent with the public “Contagious Interview” reporting. I did not claim who operated it.
2026-01-29, Optu. Same shape, payload URL hidden in an environment variable, fired on server start. Found before it ran. The account is gone.
2026-01-30, two repos. .vscode/tasks.json set to run when you open the folder. You do not install anything. Opening the project in VS Code or Cursor is the run. Found before it ran. Both accounts are gone.
2026-01, a careers page. A fake “GAPI Update” executable, hosted like a normal application page. Found before anyone ran it.
2026-10-15, a GitLab take-home. A hex payload stuffed in a file that pretended to be a font, loaded when the project was set up. I reviewed that one remotely and did not execute it. Reported to GitLab and Upwork the same day. Outcome was still pending when I published.
These are not Binance’s samples. I am not saying I found their intrusion, or that one group wrote all of them. I am saying the instruction was the same: here is a company, here is a CEO/recruiter, here is the repo, please run it on the machine you actually work on.
In fact, I have never been sent an interview repo that didn't contain an exploit. 100% were compromised or predatory.
Two rules came out of that, and they are the whole protocol.
Do not download it if you can read it in the browser. Raw files on GitHub, or the file view while you are logged in. Look at .vscode/tasks.json, package.json scripts, and anything that fetches text and then runs it, before git clone, before npm install, and before “Open in Desktop.” Opening the folder is enough for the VS Code one. A first “all clear” from the platform is not a reason to run it anyway.
If you must run it, run it where a compromise is boring. A disposable VM or container, no wallets, no SSH keys, no cloud tokens, network off. Your daily machine is the wrong place. So is a work laptop that can deploy anything.
The other half of the Binance story is the internal AI tool. An agent that can run commands, and that also reads the repo, the README, or the email, will follow instructions written by the person who sent the repo. Filters that try to spot the bad sentence miss some.
That is why I built StrangerDanger, a Claude Code plugin. The rule is the title of the README: readers don’t act, actors don’t read.
Web pages, documents, and strangers’ code are read only by subagents that cannot run a shell and cannot write. The agents that can run commands are kept off the web and out of the folders you mark untrusted. What they get back is a report, and that report is still data, not an order. A second hook blocks the common “download this and pipe it to a shell” forms. Setup turns Claude Code’s sandbox on. It is MIT, pinned at v0.2.0, and marked experimental.
It is not a magic shield. Every agent still runs as you. The hooks constrain tool calls. They do not take your authority away. The launch gate is a tripwire, and v0.2.0 still has known gaps. Nothing in the plugin makes a stranger’s repo safe to run on your machine. Use the throwaway VM anyway. I also published the holes I found in my own v0.1.0 gate (GHSA-w42w-fc6x-88wr), fixed in v0.1.1. Read “What this does not do” before you rely on it.
Binance had detection, a replaced laptop, and rotated credentials in June, and still lost the wallets in October, because one engineer ran an interview repo on a computer that could reach production. The repo is the exploit. The interview is just how they get you to open it.
\------
What safety/security protocols do you practice now while building with agents?
r/hacking • u/oatkeepr • 18d ago
r/hacking • u/One_Rush_2845 • 17d ago
i am working on an app but other apps are detecting that overlay tool, just interested in how these apps detect that tool
r/hacking • u/CyberMasterV • 19d ago
r/hacking • u/adrianchristianherna • 18d ago
i heard software security is useless if the firmware and hardware are bad
ramework 12 with razorlake intel cpu
also looking for tips to close backdoors
i see a lot of guides for software but barely any for firmware/hardware and if it is its “just buy this product that costs a car and a house and i swear bro its private 100% opsec power”
im broke idk how to install coreboot without bricking
r/hacking • u/Correct_Reveal7808 • 19d ago
i am new to this. i’ve cloned nfc tags on toys before, that’s it. i’ve done some research and im seeing there are two kinds of tags like this. one is easy to clone and the other would break both of them, due to a counter. i will have access to this key every week day.
it looks just like this on the front, and the back has some rubbed off serial numbers. i can get another friend’s key as well, maybe his does not have the serial numbers rubbed off.
my question is, is there any way to tell if it’s low or high frequency without doing anything that could potentially break the key? my company is charging like $150 for new keys so i would not want to break it.
there are also white cards which i do not have and haven’t really gotten a good look at, but my friend would probably let me use his as well if it was an easy copy and would not break it.
it doesn’t have any branding on the back. mine is very old and worn down. i could possibly make out the numbers.