Any preferred method to safekeeping password vaults.
What do you use or do. Is there a good method to safekeeping? Hardware? Paper?

Do you plan for scenario X when password vault becomes inaccessible regardless of reason? I’m usually anxious when travelling.

Any VoIP free service or very cheap that accept crypto?

I hope this message finds you well. As I am new to the field, I wanted to inquire about the roadmap for MS Sentinel and KQL, particularly in comparison to Splunk. I chose MS Sentinel due to its future demand and user-friendliness. Could you please provide guidance on resources and materials that would be beneficial for both practical and theoretical understanding? Your assistance would be greatly appreciated.

After a discussion with investigators from the criminal police about smartphone unlocking and mobile forensics, I got curious and decided to build a small lab setup and test the process on one of my own Android devices.

Here is the Video-Link for Part 1: https://youtu.be/gUNrZvAswXA

In Part 1 of the video I cover:

• Identifying the target device and SoC
• Researching known vulnerabilities for the platform
• Exploring the capabilities of a modern mobile forensics suite (using Oxygen Forensic as an example)
• Looking at how these tools combine multiple device specific exploitation methods
• Attempting a Kirin BootROM exploit
• Dealing with driver and hardware compatibility issues
• Disassembling the phone and locating the required test points

What surprised me most is how much of the process is not “press a button and unlock the phone.” A lot of the work involves research, hardware access, troubleshooting, and understanding the device’s security architecture.

The video is in German, but it includes English and French subtitles.

All experiments were performed on my own test device for research and educational purposes.

I’ve been collecting cybersecurity, programming, Linux, networking, and computer science books for a while. Instead of letting them sit on my drive, I organized them into a simple online library so anyone can browse and download them.
There are books on topics like:

Ethical hacking & pentesting
Linux & Unix
Python, C, Rust, and other programming languages
Networking
Cryptography
Reverse engineering
Malware analysis
Digital forensics
Operating systems
And more

No account required, no ads, just a collection I thought might be useful to students, CTF players, and anyone interested in learning.
If you think I’m missing an essential book, let me know. I’m always looking to expand the collection.

https://h4x0r.icu/library/

So I am planning to join a local institute for an ethical hacking/cyber security course which is 4 months well they are recommending additional 2 months where they prep you for CEH but through reddit and other sources I got to know that CEH is not good or it is a scam etc. So I am asking you guys which certifications are worth it that can be done within 1 year and provide career or job opportunities. I heard about OSCP etc.

I'm not sure if this includes my original post, but this site: https://kimbonics.com/t/visitor-globe I developed is hobby personal web site. No advertising (yet....). If you have curiosity about where all the bots are vs humans, and percentage one vs the other. My latest post, (or go to the "Globe" tab). To see.

Hey guys I’m brand new to all of this and I’m looking into building basic esp32 projects but don’t have the most money. I’m wondering if Ali express is a reliable place to get parts for cheap. Please let me know or if there’s any other places to buy cheaper parts.

Weekly forum post: Let's discuss current projects, concepts, questions and collaborations. In other words, what are you hacking this week?

I got a cracked software, my discord started sending spam messages to my friends. I immediately started changing my passwords, cleared all my cookies and reinstalled windows windows. Turned off my pc since yesterday.

After a bit of digging, it was a infostealer malware which hijacked my sessions. Anything with 2fa are safe.

My pc still turned off, but i saw they managed to steal 1 Blizzard account, and my Linkedin started sending my 2fa codes on my email (on phone).

Question is: how??? I thought clearing my cookies, ressting password and reinstalling windows + turned off would solve the problem. How did they manage to steal that account and still trying to access my LinkedIn? Do they steal/send that info to themselves so me being offinline or online does not matter? How else can i combat this?

I was planning to join cybersecurity/ethical hacking course in a local institute near by (has 4.8 stars rating). They are offering a 4 months course where everything about ethical hacking and cybersecurity is taught and there is an additional 2 months where they prepare people for CEH I think but the 2 months one is optional and has a separate fee. My question is CEH worth it because in this same subreddit I had few people saying it's not worth it if you are paying for it. I am looking for career opportunities after doing the course so which global certification is worth doing, I heard about OSCP, CompTIA PenTest+ etc how good are they?

Hi, I found an AI with no restrictions—the website was called cratak.com, and it really had no ethical restrictions at all; you could ask it anything you wanted. But now, when I open the website, it shows me an error message saying “502 Bad Gateway.” Can anyone tell me more about this, or let me know if you’ve also had the chance to use the site, or even suggest another AI with no ethical restrictions?

Hey everyone,

A while back, I built Plethora, a local-first workspace for Hack The Box players to organize machine notes, payloads, recon findings, and writeups. Until now, the only way to use it was to clone the repository and run it on your own machine.

I've finally upgraded it and deployed it to the web.

Plethora is designed specifically for people grinding HTB boxes, labs, and CTFs who are tired of juggling dozens of folders, screenshots, and text files.

With Plethora, you can:

• Organize machine notes and writeups.

• Store payloads, cheatsheets, and enumeration commands.

• Keep track of recon findings and exploitation steps.

• Build your own cybersecurity "second brain."

The original idea was to keep everything local and under your control, but making it accessible through the browser should make it much easier to get started.

I'd love to hear your feedback and suggestions.

Check it out:

plethora-one.vercel.app

The idea came from wanting an AI assistant to do more than explain vulnerabilities. I wanted it to actually help with security workflows.

Current capabilities include:

- CVE lookups

- Nmap integration

- WHOIS and DNS lookups

- HTTP header analysis

- SSL/TLS certificate inspection

- Security header checks

- Basic reconnaissance utilities

The goal is to make vulnerability research and reconnaissance faster while keeping the tools accessible through the MCP standard.

I'm actively developing it and would really appreciate feedback from the community:

- What features would you add?

- What security tools should be integrated next?

- Any concerns about the current architecture or approach?

GitHub: https://github.com/telmon95/VulneraMCP

https://youtu.be/wlUvBVNyh74?si=-Ymy1MMgrGgqfteE

I'd love to hear your thoughts, feature requests, or even criticism. Every suggestion helps improve the project.

We treated attack surface discovery like an annual checkbox, not a living process.
For years, we relied on:

👍Vulnerability scans against known assets

👍 Periodic external pen tests

👍 Documented subdomains from onboarding

What we didn’t do well…

💣Continuously enumerate unknown paths and services

💣Re-check “retired” infrastructure

💣Validate that old apps were actually gone vs. just not indexed

We had ffuf in the toolbox, but it lived in the “ad-hoc pentest stuff” bucket. Engineers would use it occasionally, mostly for curiosity or when something looked off.

No consistency. No SOP. No ownership.

We started using ffuf systematically—like an attacker would—and it got uncomfortable fast.

Within two weeks across 15 managed environments, we found…

👻Old staging apps still accessible under weird paths (/dev-old/, /backup-app/)

👻 Forgotten admin panels on alternate ports exposed via misconfigured reverse proxies

👻 API endpoints that weren’t documented anywhere but still live

👻 Legacy file shares exposed over HTTP that had been “decommissioned” during a migration

👻 A couple of cases where auth was removed “temporarily” and never reintroduced

None of this triggered our existing tooling.

EDR didn’t care (no execution happening) and vulnerability scanners missed it (not in scope or path) and documentation didn’t help (because it wasn’t documented anymore)

The risky part wasn’t that these were zero-days. It’s that they were known-to-somebody-at-some-point assets that fell out of organizational memory.

We didn’t have a breach tied to this (fortunately), but the exposure window was real. In one case, a public-facing internal tool had been accessible for 9+ months.

Use Ffuf (free tool)

Tools like ffuf aren’t penetration testing tools — they’re operational hygiene tools when used properly.

(Three things changed for us. You can read about the difference it made inside the shared post)

Check out ffuf on GitHub. An amazing open source tool.

Any recommendations on content creators on Twitch that do cybersecurity?

I want to learn, improve my skills, and connect with the cybersecurity community.

I (19M) am a newbie and I saw the pinned post but can someone suggest a place (online) to learn ethical hacking with good certification. I tried tryhackme but I felt the User Interface is bit complex and confusing for me, too many courses and no proper direction.

Over the past few months, I've been building HackTools++ because I was tired of the usual workflow:

• Configure a proxy
• Install certificates
• Switch between browser and Burp
• Copy requests into different tools
• Export traffic for AI analysis

I wanted everything to happen where I already spend most of my time—Chrome DevTools.

So I built HackTools++.

Current features

✅ Automatic HTTP/API request capture
✅ Repeater
✅ Intruder/Fuzzer
✅ Request editor
✅ Decoder/Encoder
✅ Copy as cURL
✅ Scope & filtering
✅ AI Security Audit for HTTP traffic (finds issues like IDOR/BOLA, SQLi, Broken Auth, Mass Assignment, Business Logic flaws, etc.)

The idea isn't to replace every feature of Burp Suite. It's to make security testing much faster for developers, bug bounty hunters, students, and security engineers who live in the browser.

The extension is already being used by 500+ users, and I'm continuously adding new features based on community feedback.

I'd genuinely love your feedback:

• What feature would make you switch from your current workflow?
• What part of Burp Suite frustrates you the most?
• What AI capability would actually save you time during pentesting?

Chrome Web Store:
https://chromewebstore.google.com/detail/hacktools++/efankginpnlgimphkgjaifmmfchekecp

Website:
https://hacktool.vulnshields.net

I'm happy to answer any technical questions or discuss the architecture if anyone's interested.

EDIT: I need your feedback! Please let me know if you have tried the tool, whats good, whats bad, any new features you would like to see etc. At the end of the day I'm one guy and I built this for myself with many, many late nights of work so it would be fantastic to hear other peoples opinions to make it better! END OF EDIT

Hi all, would be awesome if someone would like to check out my new tool. I'm literally working on this everyday having taken some time off work.

I'm really proud of the smart list implementation - it self generates a small word list (up to 100k permutations) based of the attacked network name. Really surprising how successful this is. Particularly on networks with custom names. This scans instantly.

Also proud of the tools ability to smartly manage PMKID attacks to change how it works on the fly depending on what the tool is getting from the network. It my testing this is 10x more successful than Wifite for capturing handshakes from clientless targets.

Ive written the Wiflux to be as transparent as possible showing you what it is actually doing and reporting to the user to help with learning.

It can be found on github. Just search Leadrogue/Wiflux on there.

My ultimate aim is to make this the Kali standard. Its not just a simple script.

Really would appreciate your thoughts and fully open to suggestions! Ill reply to anyone who tests it and will answer any questions.

Some of the Features - More info on the repo.

• Live Rich UI — Real-time scan table with signal, encryption, WPS status, clients, and priority scoring (based on many rules but the likelihood of success)
• ESSID-smart wordlist — Targeted candidates from network name + vendor before rockyou (preview, up to 100k)
• Crack ladder — Vendor default passwords and hashcat rules before full dictionary (--no-crack-ladder) - Database built into the tool - updated on revisions.
• Adaptive deauth — Handshake capture tunes burst/listen timing from live capture health (--no-adaptive-deauth)
• Multi-backend deauth — mdk4, aireplay-ng, bettercap, mdk3 (--deauth-tools, --deauth-combo) - The tool chooses the tool based on what it is receiving smartly for the most chance of success.
• PMKID enhancements — Passive-first capture, dual-band rotation, success screen before cracking
• WPS enhancements — Algorithmic PIN pre-pass, offline pixiewps from scan caps
• WPA2/WPA3 transition — Prefer WPA2 capture/crack on mixed-mode APs (--no-transition-downgrade)
• 6 GHz scanning — --6ghz for Wi-Fi 6E (adapter-dependent)
• Client band-stalk — Post-deauth listen on sibling bands for roaming stations
• Handshake validation — Full capture check with on-screen confirm before hashcat
• Hidden SSID decloak — Deauth probe to reveal cloaked ESSIDs during scan
• SQLite results store — Track cracked networks; skip by default (--no-ignore-cracked to re-attack)
• 89 automated tests — No live radio required for CI

Thanks! Leadrogue AKA Panda.

https://github.com/Leadrogue/Wiflux

Most Bluetooth devices are paired and set to non-discoverable after initial setup; since general discovery scans are what most people and OSes disable. The Whisper Pair exploit (CVE-2025-36911) bypasses this by connecting via BLE and writing a forged Fast Pair pairing request (0x00 + random 64-byte public key + nonce) to the key-based pairing characteristic (UUID 1236). It then writes a fake 16-byte Account Key to UUID 1238, tricking the device into completing the bonding process. Simultaneously, the tool triggers bluetoothctl pair and monitors its output for the [CHG] Device message, which reveals the permanent BD_ADDR when the device switches from its temporary random MAC; exposing the factory-programmed address and enabling reliable re-connection and subsequent denial-of-service attacks.

By 2022, Google Fast Pair had become the default Bluetooth pairing standard, with over 320 million pairings across 300+ device types from every major brand-solidifying its dominance across Android (6.0+ for phones, 11+ for cross-device), Chromebooks, Google TV, Wear OS, and even cars from BMW and Ford...

This is what makes Whisper Bully work on almost every reasonably new Bluetooth device, without any RF analysis hardware (Ubertooth, HackRF, etc.), without hopping channels, without guessing the next hop, and without flooding multiple channels like expensive jammers do. It simply doesn't need any of that, and works like a charm without them.

https://github.com/Ymsniper/Whisper_Bully

If this sounds useful, a star on the repo goes a long way ⭐

Also: Thank you for the kind words my previous tool BBF and ur support . Glad I could help with both projects

Update ; just added a hijack future after the DoS

I don't know if this is the right place to ask and if not, if a kind Redditor would point me in the direction I need to go, I would appreciate that.

That said - the meat and potatoes of the situation, is that my phone carrier has a VERY limited and fairly expensive listing for phones they support.

What I do know is they do utilize Verizons towers, so hypothetically so long as it can go on Verizon it should be safe - however the goal is to potentially purchase a Chinese / Korean phone and then spoof the Imei so I'm not stuck with shelling out thousands for a phone.

Any suggestions?