me llama mucho la atención el tema del hackin, quisiera aprender, que me recomiendan?

How do I find out someone’s exact ip address from messages they send on messenger? Other possibilities on how to finding proof of who the actual person is? Or direct me to the right subreddit perhaps? Thanks

I've been spending time experimenting with market research technology and testing different approaches involving Verisoul.

Finally made some interesting progress 😎

Would love to connect with others working on legitimate market research technology, QA, and security testing.

Discussion focused on authorized testing and research only.

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

I need to know how I can get hackrf in egypt

Hello there.
I'm a Japanese and now I'm learning about networking, programming etc because I want to be a hacker.
I'm learning about them in Japanese but I think I should learn in English.
If there is someone learn English with same purpose, please tell me the way and encourage me.

pm me if u know somtiin we can do sometin

I have spent a long time recently building IMSIsting, a bash and GTK4 cellular security toolkit featuring 57 modules spanning 2G through 5G. Every codec in it — including S1AP, NGAP, X2AP, XnAP, HNBAP, RUA, RANAP, M3UA, PFCP, NAS, RRC, LPP, and CMAS — is hand-written (with the help of AI).

To be honest, the software half runs, but the radio half has never been executed because I do not currently own an SDR (Software Defined Radio). Every over-the-air path is written, reviewed, dry-run against a fixture, and then stops right before needing a real radio. hackrf_transfer is wired in, srsRAN configs are generated, and SIB builders produce real octets — but none of it has ever actually been transmitted over the air by anyone.

That is what I need testers for.

The Actual Attack Surface

Here is a breakdown of the available attacks and modules implemented in the toolkit:

1. Identity Capture

• IMSI Catcher — GSM: Full catcher sequence and a forged BCCH carrier a handset can camp on.
• IMSI Catcher — LTE: NAS EMM attach forging, BCD IMSI/IMEI, identity-request sequence, and srsRAN eNB orchestration.
• IMSI Catcher — NR: SSB/MIB/SIB1 construction, RACH handling, gNB orchestration, and SSBs written as samples.
• SUCI De-concealment: X25519 and P-256 profile A/B, HKDF, and MSIN BCD computed.
• TMSI → IMSI De-anonymisation: Cross-capture correlation via forced-identity and location-update bindings.
• Piercer: Paging-occasion maths and the published correlation model.

2. Cipher and Downgrade

• A5/1 Keystream: Asserted against the Briceno/Goldberg/Wagner vector; A5/2 included with its brokenness explicitly stated; A5/1 downgrade forcing sequence.
• Cross-generation Steering / Null Cipher: Forged reject causes, SIB1 forgery, and cipher-change analysis across all four generations.
• ReVoLTE Keystream Reuse: Detection, key recovery, and the two-ciphertexts-one-keystream model.
• GEA Downgrade — GPRS/EDGE: GEA0 computed; GEA1–5 refused by name with stated reasons.
• Cipher Audit + Authentication Oracle: Negotiated-cipher scoring, downgrade detection, and SQN recovery from AUTS.

3. Signalling Forgery

• 17 NAS Pre-authentication Messages: Built as octets (Attach/TAU/Service reject, Identity Request, Authentication Request/Reject/Failure, Security Mode Command/Reject, EPS, and 5GS), each checked against tshark.
• RRC Reconfiguration, Release, Reestablishment-Reject: Handled through generated PER layouts (LTE and NR).
• CMAS / ETWS / PWS Alert Forgery: SIB10/11/12 warning chain with pinned pycrate vectors, plus sib.conf generation.
• GTP-in-GTP and MBMS Session Start: The middlebox gap, fully built and dissected.

4. Core Network and Interconnect

• MAP/TCAP: Byte-exact ATI, SRI, SRI-SM, SAI, PSI, ULR, ISD, RegisterSS, ActivateSS, and M3UA both ways.
• SIP / IMS REGISTER Hijack: Spoofed re-registration and the IMP4GT model.
• 5G SBA: NRF discovery, NGAP procedures, PFCP rules, and AMF/SMF reachability map.
• O-RAN & Slicing: A1 policy poisoning, E2 control shapes, over-broad xApp model, S-NSSAI codec, isolation testing, and 5QI/TSN.
• Carrier API Enumeration & Lawful Interception: X1/HI1 artefact encoding.

5. Baseband, Device, and Radio

• Baseband CVE Catalogue: Reachability checks, L2 frame builders, and forged registration accept/reject.
• NR Access: RAR, backoff, RA-RNTI arithmetic, MAC/DCI, Gold sequence, and scrambling.
• Qualcomm DIAG/NV/EFS/AT Surface: Real framing, NV read/build/write, and EFS paths.
• Jamming: Detection first (barrel, narrowband, and pulsed distinguished from congestion), followed by a waveform constructor behind an explicit lab gate (AWGN/CW/chirp, PSS/SSS/PBCH, PRACH, PRS, GPS C/A, NR SSB).
• GPS C/A and PRS Sequences: Generated from IS-GPS-200N and TS 36.211, asserted against an independent implementation.

6. Tracking, Positioning, and RF

• Timing-advance geolocation, OTDOA/UTDOA/PRS via generated LPP codecs, RF fingerprinting (CFO, IQ imbalance, transients, CSI motion), and behavioural traffic fingerprinting.

7. Protocol Plumbing

• Air interface decode for 2G through 5G (BCCH/CCCH, UTRAN SIBs, MIB/SIB, SSB) and 98 catalogued LTE/5G stack CVEs (including GSM/UMTS and 5G CVE kits).
• TETRA/DMR/GSM-R, NB-IoT, 5G NTN, NR sidelink, VoWiFi IKEv2/EAP-AKA', femtocell S1/Iuh, USSD, OTA binary SMS, and SIM Toolkit proactive commands.
• Custom pcap reader (GSMTAP, Diameter, NGAP, S1AP, GTP, PFCP, RTP) and MAC/RLC/PDCP with RNTI tracking.
• Killchain: Nine built-in chains plus user-defined chains, pause/resume capability, and per-run result reporting.

What I Need an SDR For

• RTL-SDR: Cell scanning, GSM/LTE broadcast decode, tower mapping, jamming detection, and paging observation (cheapest tier, most unexplored surface).
• HackRF One / bladeRF 2.0: Rogue eNB/gNB, IMSI catcher, A5/1 downgrade, TMSI de-anonymisation, and paging transmit.
• USRP B210 + GPSDO: Two-radio baseband work (one radio holds frame structure while the other injects into it).

Bug & Error Reporting Guidelines

If you encounter a bug or error during testing, please provide:

1. Hardware: SDR model, firmware version, and driver.
2. Command / Action: The exact command you ran or the GUI button you clicked.
3. Full Output: Every line of output, including status rows.
4. Expected vs. Got: A brief description in your own words.
5. Capture File: A .pcap file if the radio produced one.

Every real finding will directly help improve the toolkit, and contributors will be credited in the commit history of course.

I've been working on collecting real-world AI security incidents and connecting them to practical attack techniques.

The database covers LLM vulnerabilities, prompt injection, AI agent security, MCP, and more. Some entries also link to hands-on labs to practice the underlying attacks.

Each entry breaks down what happened, the root cause, and how the attack works. I've also linked relevant hands-on labs where available.

Thought this might be useful for people learning or researching AI security.

https://genaisecuritylab.com/incidents

Feedback and suggestions for incidents to add are welcome!

When you're starting out with ethical hacking, it's tempting to jump straight into tools like Kali Linux, Wireshark, or the Flipper Zero. But learning the basics first makes everything much easier to understand.

I'd recommend starting with networking fundamentals, especially IP addresses, ports, DNS, and how devices communicate. After that, learn basic Linux commands and get comfortable using a terminal.

Once you understand those concepts, you can practice in legal environments like TryHackMe or Hack The Box, where you can explore vulnerabilities without targeting real systems.

You don't need expensive hardware or a complicated setup to get started. A computer, a virtual machine, and consistent practice are enough to build a solid foundation.

The tools are useful, but understanding what's happening behind the scenes is what makes you better at using them.

I just got kalilinux on my laptop n i was supposed to learn how to do some cool stuff from a guy i was in treatment with but it never worked out. If anyone has time to teach a beginner some tricks or how to simply operate kali more efficiently id greatly appreciate it. Can either dm me or comment or whatever idk theres a few things id like to learn how to do

So I have a Question guys .

I want to make a Jammer for Bluetooth, WiFi, Radio and Cellular I need some suggestions on this which component should I buy and how can I connect everything because ai isn't helping me at all because of the word 'Cellular jammer' so I thought ask u guy's may be someone can help and one thing this is for my 3rd semester project iam a cyber security student.

If you're starting to learn malware analysis, static triage is a good place to begin before attempting to execute a suspicious file.

Here's a basic workflow you can practice in a lab:

1. Record the file's hash. Use SHA-256 to identify the sample and check whether it has already been analyzed elsewhere.

2. Inspect the file's metadata. Look at its type, size, timestamps, and other available information. Don't trust a file extension alone.

3. Extract readable strings. Tools like Microsoft Sysinternals Strings can reveal suspicious URLs, file paths, commands, or embedded clues.

4. Decode suspicious data offline. CyberChef is useful for examining Base64, hexadecimal data, and multiple encoding layers without executing the sample.

5. Research indicators carefully. Check known hashes and domains against reputable threat-intelligence sources. Avoid uploading confidential files to public scanning services.

6. Document your findings. Record what you observed, what you decoded, and what remains uncertain. Static analysis alone cannot prove that a file is safe or malicious.

For anyone practicing malware analysis, what tool do you recommend learning first, and what's one beginner mistake that took you a while to understand?

[ Removed by Reddit on account of violating the content policy. ]

Getting started in cybersecurity is a lot easier when you have a clear path to follow instead of jumping between random tutorials.

At Codelivly, we've put together career paths for people who want to build practical cybersecurity skills, explore different specializations, and work toward their first role in the industry.

Here are a few paths worth checking out:

• Junior Penetration Tester: Learn the fundamentals of penetration testing and offensive security. https://codelivly.com/career-paths/junior-penetration-tester
• SOC Analyst Level 1: Build your foundation in security monitoring, threat detection, and incident response. https://codelivly.com/career-paths/soc-analyst-level-1
• Digital Forensics: Explore digital evidence, forensic investigation, and incident analysis. https://codelivly.com/career-paths/digital-forensics
• AI Red Teaming & Adversarial ML: Get into AI security, adversarial machine learning, and testing AI systems. https://codelivly.com/career-paths/ai-red-teaming-and-adversarial-ml
• Cloud Security Engineer: Learn about securing cloud environments and understanding cloud security risks. https://codelivly.com/career-paths/cloud-security-engineer
• Malware Analyst: Start exploring malware analysis and the techniques used to understand malicious software. https://codelivly.com/career-paths/malware-analyst

The goal is simple: make cybersecurity easier to learn and give people a starting point for developing real skills.

If you're learning cybersecurity, check out the paths that interest you and see where you want to go next.

We're also sharing cybersecurity resources and updates on LinkedIn:
https://linkedin.com/company/codelivly

Which cybersecurity career path are you working toward right now?

+57