What is it?

A GTK4 desktop GUI for Linux that puts the wireless assessment workflow in one place. 57 modules: Wi-Fi, Bluetooth, RF, router side, and network MITM. Every module is a standalone shell script; the GUI is a view over them, so you can call any of them directly and script them.

Why it's different

Most wireless tooling is deep in one lane. Aircrack-ng is Wi-Fi. Bettercap is network MITM. Bluetooth tooling is Bluetooth. An assessment means five tools, five config files, and no shared view of anything.

To be straight about it: this is partly a wrapper. Responder, mitm6, mdk4, hcxdumptool and hostapd are underneath, and I'm not pretending otherwise. What I built is the integration, the hardware detection, and the reporting. And there are a handful of things here you won't find in the usual tools at all.

Some of what's in it

Wi-Fi: Recon, deauth, handshake and PMKID capture, WPS including Pixie Dust, WPA3 and Dragonblood, WEP, Enterprise 802.1X, PMF bypass, KRACK, FragAttacks, Evil Twin, Karma, beacon and auth floods, Wi-Fi Direct, client isolation testing, SSID overflow.

MITM and credentials: Responder, mitm6, ntlmrelayx, Router Advertisement poisoning, ARP MITM, rogue DHCP, USB Ethernet MITM.

Router side: TR-064, HNAP, UPnP, SNMP, DNS rebinding, web UI, recovery TFTP and UART.

Plus Bluetooth, sub-GHz, LoRa, Zigbee, Thread, NFC, drone remote ID, and the analysis side: capture analysis, fingerprinting, geolocation, wordlists, live traffic, passive IDS.

Things you won't find elsewhere

Frame-level jamming. Not a deauth flood — actual reactive jamming, carrier-sense manipulation and FCS corruption, driven through a modified Atheros driver. This needed porting modwifi to kernel 7.0, which is why almost nobody ships it. You can jam one access point's beacons while leaving the rest of the channel alone.

SSID overflow with real IE-length control. Beacons whose SSID exceeds the 32-byte limit, carrying injection payloads in the same bytes. The published ESP32 tools can't do this — WiFi.softAP() truncates at 32, so they all list it as future work. Building the frame by hand means the length byte is independent of the content, which is the case that actually matters.

Router Advertisement poisoning. mitm6 does DHCPv6 and deliberately skips Router Advertisements, so a network with no DHCPv6 in play is untouched by it. This does RA/SLAAC: one forged packet reconfigures every host's default route and resolver.

Client isolation bypass. Gateway bouncing, port stealing, broadcast reflection, plus an inter-NIC relay to hold the bypass open. From the AirSnitch work (NDSS'26).

USB Ethernet MITM. RNDIS-based, PoisonTap-style, over a USB port.

Router recovery and console. Recovery-mode TFTP, UART/U-Boot guidance, offline flash image parsing. Unusual to find in a wireless tool.

Multi-node capture. Drive a fleet of remote nodes — Pi, VM, laptop — and correlate what they see.

The one I'd argue matters most: it's built to tell you when it failed. Every module has a --selftest. Hardware-gated modules name the hardware they're missing instead of returning an empty result. A module that reports OK while the target is untouched is worse than one that fails loudly, and that's the bug class I'm hunting.

The hardware

Nothing here is needed to build or launch the app. But most of it won't do anything without at least one of these, so it's worth knowing what each piece buys you.

Essential — a Wi-Fi adapter that can inject. Atheros AR9271 is what I built and tested against: TP-Link WN722N v1, Alfa AWUS036NHA, Technoethical N150.

Intel adapters will not work for anything involving injection. The app detects iwlwifi and tells you so instead of failing quietly, but it will refuse. Monitor mode alone isn't enough. Without one of these, you can browse the interface and read captures, and that's about it.

A second Wi-Fi adapter — for client isolation testing. That module needs two interfaces associated at the same time, one acting as the victim and one as the attacker. Any managed-capable card works as the second; it doesn't need to inject.

Bluetooth adapter — for the eight Bluetooth modules. Classic and BLE recon, SSP, advertising forgery, fuzzing, mesh, tracker hunting, HID injection. A recent adapter is preferable; some of the older CSR dongles won't pass BLE advertising data through.

802.15.4 radio — for Zigbee and Thread. A CC2531, CC2652 or nRF52840 dongle, flashed with sniffing firmware. One radio covers both, because Thread and Zigbee share the same physical layer — they're different stacks on the same silicon. This is also the hardware that gets you toward Matter.

SDR — for RF spectrum, sub-GHz, LoRa and drone Remote ID. An RTL-SDR is the cheap entry point and covers sub-GHz receive. A HackRF adds 2.4 GHz coverage and transmit, which you need for anything that isn't passive. Note that sub-GHz transmission — replay attacks and the like — needs TX-capable hardware; an RTL-SDR can only listen.

NFC reader/writer — for the NFC/RFID module. A PN532 or ACR122U handles NDEF and MIFARE work. A Proxmark3 if you're going past the tag structure analysis into proper card research.

USB-to-UART adapter — for router console access. CP2102, CH340 or FTDI. This is what gets you a U-Boot prompt on a router's serial header when recovery mode won't hand it to you. Worth having a set of dupont leads and, for board-level work, SOIC clips.

GPS receiver — for wardriving. The wardriving module drives Kismet with gpsd, so any receiver gpsd supports works. USB or Bluetooth both fine.

What hasn't been tested yet

Bluetooth, all of it except recon. I don't have an adapter, so none of those eight modules has run against real hardware. The code is written and reviewed, but that's not the same claim as working.

Same for sub-GHz, LoRa, Zigbee, NFC and drone remote ID. No SDR, no radio hardware here.

Thread does offline pcap analysis fine; live scanning is untested, no 802.15.4 radio.

Jamming needs a modified driver and firmware that isn't shipped. It'll tell you it can't find the driver. That's correct behaviour, not a bug.

What I actually want from testers

Run it, and tell me:

Does it start on your distro? GTK4 version, Wayland vs X11, missing dependencies.

Does it get your adapter right? Wrong hardware detection is worse than none.

Modules that report OK but did nothing? This is the one I care about most.

Anything that crashed or wedged your adapter.

And the most useful thing: tools/diag.sh --collect produces a report with distro, kernel, GTK version, adapter and driver, injection capability, dependencies, and per-module selftest results. It replaces MACs and SSIDs with placeholders and strips secrets before writing anything, and it never touches the loot folder. So you can paste it without leaking your neighbours' network names, which I'm not going to ask you to do.

I tried qwen on its chatbot and it did help I heard about downloading it on computer To do what i want is that true

I want to start sc_m and phi&h

I am talking about hacking groups which are not backed by state.

If I am not wrong, there main goal is money...
So they either directly hack for money or for sensitive information which they can sell for money. Am I right?

I am curious, if they get information - then where do they sell this information at? And who purchases them? Are there any market place for such thing?

Last time I checked darkweb, it was entirely dead... Like almost all the sites on Hidden wiki were not working or just seemed too scammy..

Moreover, many banks and other financial institutions are backed by AWS, GCP, Azure or some security firm which makes them too secure to be penetrated.

Not to say, the current advancements in AI models (where the latest advanced model without guardrails have been only released to these few companies and banks) - this makes it almost impossible for almost black hat hackers...

Like, the most advanced model (that too without guardrails) are being used by large companies and banks to continuously find security issues and fix it.

So how hackers are playing a loosing game (against world's best security researchers and best models).

Now, let's say that hackers were able to get the money, but but I was seeing the whitewashing money process and it was extremely difficult and too exhausting.
Don't that make them loose more than what they would have if they paid taxes?

So like those black hat hackers would rather be more wealthy if they were security researchers (not to add), they would have been world class.

When I asked LLM -
It told that their primary target is not to penetrate companies security system directly (as shown in movies) but executives...
Now this makes me even more curious like how is it possible to scam executive with such an elite pedigree and achievements that too in a condition where his every movement is tracked carefully... How can they even fall for scams or phishing attack or something similar?

(I am sorry for my crooked english and not able to provide tldr as every sentence seems important.)

Please delete if not allowed, absolutely no hacking experience. i had an exam at my university last week via lockdown browser , and my girlfriend managed to find a discord on Reddit of hackers where they were able to block ultraviewer and managed to control the entire exam from my HP without raising any red flags on lockdown and they took it for me while I sat in class acting like I was the one taking it. I’d love to learn or even purchase whatever software needed for future exams if needed.

https://github.com/rianhanft/Rians_Evil_Portals_For_Marauder

I've been working on a more advanced generation of captive portals — all single .html files under 20 KB — that go well beyond the basic login screen. These let the target navigate a fully functional menu with working tabs, interactive sheets, and two additional sign-in paths beyond the standard email/password flow (victim can pick between logging in to Google or Apple as other options), both built with CSS-only overlays so they work within the esp32-c5’s constraints. Took a fair amount of iteration to get everything behaving correctly on the Marauder mini V3 and V8, but they should also be solid on any microcontroller running the marauder firmware or any firmware capable of launching captive portals.

My repo now has 400+ portals (not all are built around an advanced framework), each branded and built specifically for a real corporation — coffee shops, ISPs, banks, airlines, and more.

Please only deploy on networks you have explicit written permission to test. The intent behind this repo is education and authorized security assessments. It's a useful tool for security awareness presentations and red team engagements. It is not intended for unauthorized use and I take no responsibility for misuse.

PLEASE LEAVE A STAR ON THE REPO IF YOU ENJOY THE PROJECT AND WANT ME TO CREATE MORE🥹⭐️

If you run into any issues, feel free to DM me here on Reddit.

Hi everyone! I’m a fan of web-based games and wanted to show off a project I’ve been lovingly working on for about two or three years though it’s taking a while since I don’t have much free time.

Anyone who played *Hacker Experience* remembers the feeling: typing in an IP address, cracking a server's password, breaking in, wiping your tracks from the logs before anyone noticed, and walking away with money from a bank account that wasn't yours. It was a game that looked simple on the surface but was massive underneath. The creators released the *Legacy* code under an MIT license, and I decided to build a faithful remake for modern browsers. All credit for the original game goes to them.

How it works

You start out with a weak computer, a few basic programs, and an IP address. From there, the game's internet is yours to explore:

Browse via IP addresses and discover banks, corporations, ISPs, puzzle servers, a download center, the black market, and even the agencies that will hunt you down.

Hack in using brute force pitting your Cracker against the target's Hasher—or via exploits, using port scanning and vulnerabilities in FTP and SSH.

Cover your tracks.Everything you do leaves a trace in the logs—both yours and the target's. Forget to clean up? Someone will find your IP.

Install viruses that generate income through spam, warez, and Bitcoin mining, then come back later to collect the profits.

Take down servers with DDoS attacks and crash other players' hardware.

Upgrade your machine: CPU, RAM, hard drive, connection, external drives, and extra servers.

Research and develop software at the university, earn certifications, and upgrade your programs to newer versions.

Complete missions for shady clients: deleting files, stealing data, transferring money, and taking down competitors. There are also daily contracts, storyline arcs, and weekly events.

Everything involves real-time processing. In the Task Manager, you can see your processes running simultaneously, just like in the original.

True multiplayer

Other players share the same internet space. They can hack you, read your logs, steal your money, and tamper with your viruses. You can form or join a clan, wage war against other clans, and collaborate on clan projects. There are rankings, a Hall of Fame, nearly 90 badges, and news updates covering events in the game world.

And watch out: if you make too much noise, the FBI and Safenet will come after you, complete with a "Most Wanted" list and a bounty on your head.

Rounds

The game operates in seasons. Each round ends when someone successfully launches "Doom" the virus that takes down the entire internet and then everything starts over. You keep your badges and your account.

Riddles

For puzzle lovers, there is a trail of riddles hidden across servers on the internet. It features unique minigames: cracking a safe by spinning a dial, decoding signals (ASCII, Caesar cipher, binary), and others I won't spoil here.

What's different from the original

It works on mobile, with light and dark themes and text available in both Portuguese and English.

New missions, storyline arcs, events, and locations on the internet.

A fresh look, with custom artwork for locations and NPCs.

The game is constantly updated. Features like customizable profiles, animations for key moments (such as being hacked or hunted by the FBI), and more are on the way.

Important

It’s free, ad-free, and requires no download it runs right in your browser.

All "hacking" is fictional. It’s all just game rules contained entirely within the game itself so it doesn't affect the real system.

It’s for ages 18 and up.

It’s a beta, so there will be bugs. If you find any, let me know. A "report bug" button will be added to the game soon, with rewards for those who help out.

I’d really love to hear your thoughts, especially from those who played *Hacker Experience*: what feels similar, what’s improved, and what’s missing.

you can acess by search zerotraced on google.
or you can acess on the link https://zerotraced.com

Not better than WhatsApp, Signal, SimpleX, Cwtch or Ricochet. You definitely shouldn't use this replace any of your existing apps or services. It's far from finished. Unaudited and unreviewed. If you want to test it out, please use it responsibly.

I'd like to share what I'm working on and interested if anyone wants to share feedback on the approach.

It's a fairly a unique approach and architecture in contrast to the typical approach with mainstream messaging apps. To put it briefly, its a Dioxus PWA with a Git-server backend which can be used to establish a webrtc connection between browsers.

https://glitr.io/docs/technical/roadmap

So far, it's only the browser-based version that's available for testing. The webapp approach has nuances and limitations. I hope to soon release the APK and TUI when they are ready (they introduce the TOR capabilities (not possible on a browser)).

I’m the author of Super Trouper, a single-binary MCP server that exposes Frida to coding agents for authorized app reverse engineering. It lets an agent connect to a device, inspect apps and processes, manage sessions, and run instrumentation scripts without a Python-based Frida setup.

We released v0.4.0 a few days ago; it updates the bundled Frida Core DevKit to v17.19.0 and adds four MCP tools: memory_read and memory_write for working with memory in an attached process, plus module_list and thread_list for inspecting loaded modules and threads. app_list and others now have several query scopes, and we renamed the MCP tools into clearer namespaces. If you already have workflows built around the old tool names, check them when updating.

Quick catch-up on the two previous releases: v0.3.0 added npm installation, Frida CodeShare snippet search/use, and general cleanup. v0.2.0 moved the project to the MIT license, added first-party Frida language bridges for ObjC, Java, and Swift, and enabled TypeScript in scripts and evaluations.

I’d appreciate feedback from people using Frida in iOS research: are these tool boundaries and the new app-list scopes useful in practice? What’s missing or awkward in your workflow, and which features would you like to see next? Let me know what you think.

A 16-year-old bug hunter found Microsoft's internal Titan analytics API and discovered that it validated the JWT tenant, audience, app ID and user, but apparently forgot the slightly important part: validating the signature.

His AI agent spent 10 days grinding through the authentication errors. Eventually he tried admin as the username, Titan resolved it to a local admin account, and he ended up with SQL access to an environment containing an estimated 17.3 trillion stored rows across 17 analytics databases.

Microsoft fixed it and paid him a $5,000 bounty.

Some bugs are just beautiful in their simplicity.

https://github.com/mein-0/gvcidrv64 support pls

I’ve been studying comment sections on short-form video platforms (like TikTok and Reels) & keep noticing a highly coordinated automation phenomenon that I want to understand from a technical and architectural standpoint.

Whenever a trending or viral video hits a specific niche topic, a third-party account instantly leaves a comment framing itself as an organic public service announcement (e.g., naming a specific app, game, or product relevant to the video). wWithin minutes, that comment accumulates 1000s+ of likes and dozens of secondary replies, locking it into the absolute "Top Comment" slot where millions of viewers see it.

I'm curious about the engineering, scaling, & infrastructure behind how this is achieved:

1. Real-Time Detection: How do these scrapers monitor platform uploads or specific hashtag triggers so quickly without constantly tripping API rate limits or triggering blocks?
2. Network Infrastructure: How do operators coordinate the footprints of hundreds of "zombie" or secondary accounts to deliver likes/replies simultaneously without triggering the platform’s anti-fraud algorithms? Is this heavily reliant on residential proxies, anti-detect browsers or cookie-session farming?
3. Algorithmic Exploitation: What specific engagement signals (like early velocity or reply density) are they taking advantage of to fool the ranking algorithm into permanently pinning an artificial comment?

I’m looking to understand the technical mechanics of how these shadow networks operate. Any insights, technical breakdowns or open-source case studies would be greatly appreciated!

Ramsoftware is 1337

Just found these in my photobucket while looking for so.e old screenshots.

which lets me search up leaked database and give me all the information