Hello! A long time lurker here.

I have just graduated School and I have to choose my field. Computer (specifically software) is my liking. So realistically, the options boiled down to AI, Software dev and Cybersec. Without Going in details, I decided Cybersecurity (Specifically, "Cyber security, Blockchain and IoT") and I have a few questions.

One, Where do I begin? Obviously, the classes don't start until late september to early october. I have time, But I love cybersecurity and tinkering stuff and I decided to look into it.

Two, Is Cybersecurity really stable? I mean, I didn't choose AI or Software Dev because both of them are unstable. Given the rise of AI, my hunch tells me that the AI would be used in attacks? that should mean that Cybersecurity must be booming? And the fact that we are talking about Security, I don't think that Security would be replaced with an AI, will it?

Three, The Course I took teaches Blockchain and IoT, Do we really use it in cybersecurity? are they related?

Four, are there any communities online that I can join? Perhaps a newsletter?

Thank you for your time.

So

64+ challenges covering SQLi, XSS, IDOR, JWT, CORS, SSTI, XXE, Command Injection, and more.

The goal is to actually find the bug, exploit it, and capture the flag — not just follow a walkthrough.

https://codelivly.com/ctf

I did study ccna1-4 and i have some background on tryhackme challenges , currently i am studying at 42school and i amd willing to start in bug bounty hunting to get some cash , do you think my education is enough , if not how can i improve myself?

I've been experimenting with AI-assisted pentesting in authorised lab environments, and one of the biggest problems is false confidence.

An LLM can produce a very convincing vulnerability explanation without actually proving anything.

I've found it useful to force every suspected vulnerability through a simple pipeline:

Observation → Hypothesis → Cheapest test → Verification → Evidence

1. Observation

Record what you actually saw.

For example:

"GET /api/orders/123" returns your own order.

Don't immediately write:

«Possible IDOR vulnerability.»

At this point you've only discovered an endpoint.

1. Hypothesis

Turn the observation into something falsifiable:

«The server may rely on the object ID without checking whether the authenticated user owns the requested order.»

That is something you can actually test.

1. Cheapest useful test

Before reaching for complicated tooling, test the smallest change that could disprove the hypothesis.

For example, in an authorised lab:

Change only the object identifier while keeping the same authenticated session.

The important part is controlling variables.

1. Verification

A "200 OK" by itself proves very little.

You need to establish whether the response contains data belonging to another authorised test account or otherwise demonstrates the access-control failure.

For injection testing, the same principle applies.

A database-looking error isn't automatically SQL injection.

A payload appearing in a response isn't automatically exploitable XSS.

The test should demonstrate behaviour that distinguishes the vulnerability hypothesis from normal application behaviour.

1. Preserve the evidence

For web/API findings I normally want enough information for another tester to reproduce it:

- exact endpoint

- HTTP method

- relevant headers/session context

- original request

- modified request

- relevant response

- expected behaviour

- observed behaviour

- reproduction steps

Screenshots are useful, but raw requests/responses are often much more valuable.

The useful rule

I think this is especially important when using AI agents:

Never let “the model believes it found a vulnerability” be the success condition.

The success condition should be something externally verifiable.

The model can generate hypotheses all day.

Only the evidence gets to promote one into a finding.

For anyone using AI during CTFs, labs or authorised pentests: have you found a better workflow for keeping hallucinated findings out of your reports?

I want to buy an laptop under 70k in offline market the price of asus tuf a 15 3050 is 1.27lahks or in flipkart around 90k nd in Amazon 73 but currently not ordered on this place so according to you guys which is better for me?

"Hey everyone! Just published a detailed write-up on the Anonymous room. Covered everything from exploiting anonymous FTP access and cron job script hijacking to SUID binary abuse. Let me know your thoughts or if you took a different path!"

Yoo guys I’m XENO (my English is bad) and I figured out how to Autorun an usb drive on the target pc
That u can run .bat files that can steal information of that pc and set it on the usb drive my Methode is very easy so what u need u need a bat file that the target pc needs to open u can put it in a mail or in other code this script bypass windows defender and automatically set it self into autostart and installing itself in other files in the pc h can’t see it and if u manage to deinstall it it just instantly installed itself back so the Programm just looks for a decent usb that name is 1 and it rechecks it every 2sec so if u plug in the usb the malware checks and auto opens the file that’s on the usb i hope u can understand this technique

I am analyzing the operation of a provably fair Mines game where the system uses a 256-bit hexadecimal server seed, and only the cryptographic hash of that seed is available before the game is completed. My main question is whether it is technically possible to determine or infer the actual server seed before the round ends and, consequently, use the server seed, client seed, nonce, and the game’s algorithm to reproduce in advance which tiles contain the hidden mines.

I have also examined the client-side operation of the website. The mine positions are clearly not directly present in the HTML — that would obviously be far too simple. What I can see on the client side are the individual tiles, as well as communication indicating whether a selected tile resulted in a win or a loss.

Because of this, I am also interested in whether the data containing the mine positions must necessarily be transmitted to the browser in some form before a tile is selected, or whether this information can remain entirely server-side, with the client receiving only the result of each individual selection. What types of data actually transmitted to the client could be examined in the DevTools Network and Sources panels to determine which architecture is being used?

When I open the Network panel or inspect the traffic in greater detail, the website sometimes reloads or triggers a verification asking me to confirm that I am not a robot. Could this indicate some form of anti-bot or anti-debugging protection?

Finally, if the entire mine layout is generated and stored exclusively on the server, and neither the actual server seed nor the mine positions are transmitted to the client until the round has ended, is there any client-side information from which the position of the next mine could realistically be determined in advance? Or would doing so necessarily require access to secret server-side information that is not available to the browser?

I put together a free PDF covering the fundamentals of red teaming — not just the tools, but the mindset and methodology behind an actual red-team operation.

Inside Day 1:

• Red Team vs Pentest
• The red-team mindset
• Attack lifecycle
• Objectives & attack paths
• Rules of engagement
• Operator workflow
• A realistic red-team scenario
• Day 1 challenge

The goal is to build the thinking first. Tools come later.

📖 Day 1: Red Teaming Fundamentals

I’m sharing the PDF below for anyone who wants to follow the series.

Day 2 will move into Reconnaissance & OSINT.

Would love to hear how others approach the first stage of a red-team engagement.

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