Hey everyone,

Whenever I do a box that involves getting WP admin credentials, manually logging into the dashboard, navigating to plugins, and clicking "Upload" to drop a PHP reverse shell always felt too slow.

I wanted to automate the process from the terminal, so I spent some time figuring out the exact curl syntax to do it. It’s a great way to understand how WordPress handles authentication and CSRF protection under the hood.

The core workflow comes down to 3 steps:

The Login: Sending a POST request to wp-login.php and saving the session cookie (-c cookie.txt).

Grabbing the Nonce: WordPress uses a nonce for security on plugin uploads. You have to GET the plugin-install.php page with your cookie and grep/awk out the _wpnonce value.

The Payload Upload: Finally, using curl -F to send the malicious zip file as multipart/form-data, passing both the cookie and the nonce.

Automating this really helped me understand HTTP requests better rather than just relying on the browser.

If you want to see the exact bash commands and cURL syntax I used, I wrote a full breakdown on my blog here: [https://medium.com/@0xShell/beyond-the-browser-automating-authenticated-wordpress-plugin-uploads-with-curl-e357cfb3ff3e].

Hope this helps speed up your workflow on your next box! Let me know if you guys have other ways you automate WP exploitation.

Not sure if this is the right place to post this, but I shared it on r/cybersecurity recently and got some great advice, so I thought I'd share it a little more widely.

This tool pulls a bunch of security information sources into one place (38 sources), and it doubles as an MCP server, so you can plug it into any of your AI agents. It's MIT licensed and written in Rust.

Paste in a CVE and it pulls from NVD, CISA KEV, EPSS, OSV, public exploit sources and others in parallel. You get a 0–100 risk score and a short "act now or later" answer, with the evidence listed so you can check it yourself. It also handles IPs, file hashes and dependency files. You can use it as a desktop app, a CLI, a REST API, or an MCP server for Claude Code, Cursor and similar tools. The AI part is optional and runs locally by default, so nothing leaves your machine unless you switch it to a hosted model. Information is only as current as the public data.

I've had this idea for a while and I'm still not sure exactly where I want to take it, so if you have any suggestions, I'd love to hear them. Feel free to contribute to the project. Thank you!

https://github.com/Fazmin/cve-intel

I'm planning to pivot into Cybersecurity over the next 12 months, specifically targeting the GRC side of things.

​I already have a background in IT support but I'm looking to pivot into a full-time GRC role within a year.

​My main goal is to spend this year learning as much high-value stuff as possible to get job-ready and land a entry-level/junior GRC or Analyst role.

​For those working in GRC or hiring for it:

​Frameworks: Which frameworks should I master first? (e.g., NIST CSF, ISO 27001, SOC 2) Should I just read them end-to-end, or is there a better way to learn how to apply them?

​Certs: Is there any entry-level cert actually worth getting for GRC (like CompTIA Security+), or should I just focus on learning controls, audit prep, and risk assessments?

​Projects: What kind of practical project or portfolio can a beginner build to prove they understand risk management and policies?

​Any advice, reality checks, or recommended resources would be hugely appreciated! Thanks in advance!

I'm a fresher stuck without proper guidance. Few weeks ago, I got assigned with a task to pentest a mobile app, I don't know anything Abt it, the setup, the methodology, etc., I don't have any senior to seek help in my org.

I spent weeks searching, watching YT tutorials.

But I couldn't understand anything. The setup itself is failing sometimes. Being an enthusiastic hands-on person and not understanding the way to pentest a mobile is a big nightmare.

I require quality guidance. Pls help me out

As someone who’s worked in cybersecurity for over eight years, across roles ranging from pentesting to vulnerability management, I’m curious: what’s motivating you to study cybersecurity or pursue a career in the industry as a beginner?

Hi all,

I’ve published a small Windows password-hashing library in Ada/SPARK: Win32_Hash.

What it does:

• PBKDF2-HMAC-SHA256 through the Windows CNG API (BCryptDeriveKeyPBKDF2), 1,000,000 iterations by default (650k–1M by type)
• Random salt, 32–256 bytes, from ProcessPrng with BCryptGenRandom as fallback; stored as Base64 (RFC 4648)
• Hash stored as 64 uppercase hex characters; separate verify procedure with constant-time comparison, fail-closed
• Every secret wiped with SecureZeroMemory plus a redundant Ada overwrite, on success and on every failure path

Verification:

• GNATprove --level=4, all provers: 186/186 checks proved, 0 unproved
• Re-verified on three GNATprove versions: Community 2021, 14.0.1, 16.0.1
• adacovex: GNATprove Platinum (186 VCs), DO-178C DAL-C achieved

Honest scope, as documented in the README: the bodies that call the Windows API directly are SPARK_Mode => Off (their contracts are checked at run time); everything around them is proved. Not externally audited — I don’t call it “secure” without that qualification. Windows only.

https://github.com/EliAvila10/Win32_Hash

Feedback welcome.

Hi everyone,

I am a Bachelor’s student specializing in Cybersecurity, and I need to complete a 3-month internship. I have already secured the internship location, and they are willing to provide me with a dedicated server, but we haven't decided on a project topic yet.

Do you have any project ideas I could work on? The project needs to be free/open-source, substantial enough to span over 3 months, and directly related to cybersecurity.

One of my professors suggested setting up OpenNebula (including template integration, automation, pay-per-use billing, etc.), but I'm worried about the lack of community support if I get stuck, especially since I'll be working on this project completely on my own.

Any suggestions or advice would be highly appreciated! Thanks!

Hey everyone,

I've been working in cybersecurity for the last 5 years, and over the past year I've been building a project called Vader-Pro-VDR, an AI-assisted Vulnerability Detection & Remediation platform.
So far, I've built:
A Go-based endpoint agent that collects system and software inventory information.

A backend API that receives and processes agent data.

AWS-hosted infrastructure for communication between endpoints and the backend.

A working proof of concept that can identify installed applications and their versions across endpoints.

My long-term vision is to build a platform that can:
Continuously identify vulnerable software and configurations.

Correlate findings with CVE intelligence.

Use AI agents to provide remediation recommendations.

Eventually automate certain remediation workflows in a controlled manner.

The challenge I'm facing isn't necessarily technical anymore. I've realised that a project of this scope is difficult to build alone.
I work remotely and don't have much exposure to the open-source community, so I'm looking for advice from people who have built or maintained open-source projects before.
Some questions I have:
How did you find your first contributors?

At what stage did you make your project public?

What communities have been most helpful for cybersecurity-focused open-source projects?

Are there common mistakes first-time maintainers should avoid?

What would make you interested in contributing to a project like this?

The repository is here:
https://github.com/Tridents10/Vader-Pro-VDR

I'm looking for honest feedback, technical criticism, and advice on how to take this from a personal project to a community-driven one.

Thanks in advance.

Hey everyone,

I've been working in cybersecurity for the last 5 years, and over the past year I've been building a project called Vader-Pro-VDR, an AI-assisted Vulnerability Detection & Remediation platform.
So far, I've built:
A Go-based endpoint agent that collects system and software inventory information.

A backend API that receives and processes agent data.

AWS-hosted infrastructure for communication between endpoints and the backend.

A working proof of concept that can identify installed applications and their versions across endpoints.

My long-term vision is to build a platform that can:
Continuously identify vulnerable software and configurations.

Correlate findings with CVE intelligence.

Use AI agents to provide remediation recommendations.

Eventually automate certain remediation workflows in a controlled manner.

The challenge I'm facing isn't necessarily technical anymore. I've realised that a project of this scope is difficult to build alone.
I work remotely and don't have much exposure to the open-source community, so I'm looking for advice from people who have built or maintained open-source projects before.
Some questions I have:
How did you find your first contributors?

At what stage did you make your project public?

What communities have been most helpful for cybersecurity-focused open-source projects?

Are there common mistakes first-time maintainers should avoid?

What would make you interested in contributing to a project like this?

The repository is here:
https://github.com/Tridents10/Vader-Pro-VDR

I'm looking for honest feedback, technical criticism, and advice on how to take this from a personal project to a community-driven one.

Thanks in advance.

Disclosure: I am the creator of OIDC Inspector and I added the FAPI 2.0 metadata signals based on the feedback on this subreddit.

I've added a FAPI 2.0 section. For each requirement of the FAPI 2.0 Security Profile that discovery metadata can say something about, it reports whether the server publishes a matching value.

Things I'd like opinions on:

1. Are any of the profile requirements I'm treating as observable from metadata actually not?
2. Which metadata fields would you want surfaced that I'm missing?
3. Is "differs" the right label when a server publishes something outside the profile (for example `client_secret_basic` alongside `private_key_jwt`)?

It's free, but it needs a free account to run scans. Link: https://contextiq.trango-compute.com/dashboard/oidc-inspector

Happy to answer questions.

I want to announce a new pentest learning platform: Knossos

I’ve been working on this lab for a bit - I’ve always wanted a better server platform for people to learn pentesting on, besides simply spinning up VMs, and I finally had the opportunity to build it.

Based on the lessons in my books, I built Knossos to have over 2 dozen servers, three networks (DMZ, Internal, Private), and 33 pentest challenges. It emulates an enterprise environment, and the best part is it’s all wrapped up in a single docker deployment. A couple commands, and you have an entire, complex network to learn hacking against.

Capture flags as you work through the network. Each flag is tied to a chapter within my book ”Professional Penetration Testing” where I teach how to perform the attack and why.

You can learn more about the free lab at https://pentest.tv/knossos

This is the lab I wish I had when I was trying to learn pentesting over two decades ago. For those that don’t know, I created one of the first exploitable virtual machines: De-ICE. I spoke on the De-ICE discs at DefCon 15, which later spawned the books - the most recent version of "Professional Penetration Testing" is the 3rd edition. This has been an incredible journey over the last couple decades, and I’m excited to bring you Knossos - the next generation of pentesting labs.

LMK if you give it a try and what you think. Thanks!

- Tom Wilhelm

Next week, we're bringing an FBI agent to our office in Utah for a candid conversation about cybersecurity, the threats we're facing, and what organizations need to know. No sales pitch, just a chance to hear an insider's perspective.

We're kicking off the morning with a networking breakfast, and we'd love to have you join us.

Come hang out in person, or tune in online. Either way, it should be a great conversation.

Free to attend. Hope to see you there!

https://zoom.us/webinar/register/5117921732126/WN_XIp2emSmS8ebHLoMGWXqzg

Title. I'm not gonna post pictures bc I dont want people thinking im marketing-- im not I just dont knoe if this is worth finishing. its just a basic CRUD skeleton I made for myself because I hate Spotify premium and when downloading music I hate organizing it in my phones files and losing functionality. Please lmk if this is something too overdone or if this is somewhat of a niche ​

Hi all,

I am just a beginner in cybersecurity and ethical hacking and I need an AI study buddy to guide me through basic concepts, CTFs, tool usage (Nmap, Wireshark, Metasploit, and so on), and network traffic at the level of packets.

Commercial chat assistants tend to block any security-related questions and refuse to answer how something works. For this reason, I have chosen the local approach.

My hardware specs:

GPU with 12GB VRAM

System RAM with 32GB DDR5

I can put the quantized 8B to 14B models fully in VRAM or load them partially, in case it is beneficial to sacrifice token processing speed for that.

What models or fine-tunes would you recommend me that know the technical stuff but do not have overly strict guardrails?

Hey everyone!

We're Exun Clan, the student-run tech club at DPS R.K. Puram, New Delhi, and we're back with the 16th edition of Sudocrypt, our flagship international CTF!

Sudocrypt is an international Cryptic Hunt x Capture The Flag (CTF) event where participants from around the world tackle a series of cybersecurity and cryptic challenges. Expect code-breaking, cryptography, and plenty of problem-solving as you work your way through the levels.

The competition is entirely online, so you can participate from anywhere in the world.

Dates: October 27–28, 2026

Prizes: With a prize pool of over $900 USD in previous editions, along with over $500 USD in goodies and prizes, Sudocrypt v16.0 promises an exciting challenge for cryptic enthusiasts and CTF players alike.

Event website: https://sudocrypt.com/

CTFtime listing: https://ctftime.org/event/3443/

You can also check out the other events at Exun 2026 here: https://exun.co/26/events

Hope to see you on the scoreboard!

Malware analysis is such an interesting field to get into (casually for now, don't want to focus on it too much since I want to be flexible as I am still a student).

But since malware analysis is essentially reverse engineering targeted for malware, and with the introduction of tools like REA + AI models getting extremely advanced to the point where any person can just prompt the AI with basic terminologies (and knows how to bypass its guardrails) are plausible, then is there any point in me learning its fundamentals and advanced stuff at this point in time, or do I just gain experience with how AI does it and be familiar with how it operates instead?

Although my gut feeling assumes malware analysis and its adjacent fields will be getting significantly harder but I somehow don't know why; just intuition?

It would be best appreciated if actual professional malware analysts or those with experience in Incident Response / Threat Hunting answer, thank you!

I want to share my recent experience with the PortSwigger BSCP (Burp Suite Certified Practitioner) exam, specifically regarding severe platform instability, their misleading claims about exam proctoring, and their refusal to provide a refund.

Candidate Background

• Completed all 273 labs on the PortSwigger Web Security Academy.
• Reached global ranking #266 on the Hall of Fame.
• Deeply familiar with the Burp Suite ecosystem and the platform's exploit methodologies.

1. The "Proctoring" Illusion vs. Reality

PortSwigger markets this exam as an actively monitored, strictly proctored certification environment. Candidates are told that their session, screen, and test windows are strictly tracked and under surveillance:

• No Active Live Proctoring: In reality, there is zero real-time human proctoring. Nobody is actually watching or monitoring your test execution live.
• No Real-Time Technical Recourse: When platform errors or browser crashes happen, there is no proctor to log the incident, freeze the exam timer, or verify that the infrastructure failed.
• Shifting the Blame: Because they don't perform genuine live monitoring, when the environment crashes, they simply claim that "your test window was closed" or that the failure was strictly an exploit error on your side. They won't even review screen or session telemetry to verify the truth.

2. Infrastructure Breakdown During the Exam

• First application: Fully solved and completed in under 30 minutes.
• Second application: Catastrophic backend failure. The remote instance started throwing backend server errors, recurrent timeouts, and the testing browser repeatedly crashed.
• I correctly targeted the password reset flow and the Host Header family, but the broken lab instance could not reliably process payloads or return tokens.

3. Forensic Evidence vs. Support Dismissal

To ensure complete transparency, I gathered approximately 50 forensic artifacts:

• Full disk-based Burp project files (.burp)
• Custom exploit and automation scripts (reset_poison.py, desync.py, etc.)
• Raw HTTP logs and terminal outputs showing backend timeouts

Despite this extensive proof, support summarily claimed that I merely failed to construct the specific Host Header bypass filter and refused to admit the environment crash. They refused any refund or further retake.

1. Current Status

• Management (Director of Intelligent Support) reviewed the ticket and upheld the refusal to refund.
• When I raised factual feedback regarding support communication in the official Discord community, my access was restricted and I was removed from the channel.
• A statutory complaint has been filed with the UK International Consumer Centre (Ticket: #91462) under the UK Consumer Rights Act 2015.
• Formal claims for both exam charges ($198.00 USD total) are currently active on PayPal.

Takeaway for Prospective Candidates

Do not rely on their claims of a "proctored" environment. If your lab instance freezes, drops packets, or crashes, there is no proctor to verify it, and support may simply blame you, take your money, and refuse to remediate. Be extremely cautious before paying for this exam.

Has anyone else faced silent container crashes or complete lack of proctor oversight during the BSCP?

Note: What they call a proctored exam is supposed to monitor your screen, but no such thing actually exists; they cannot even review the exam to verify that what I am saying is true.

Hey everyone,

When studying for certs like Security+ or just trying to wrap your head around cryptocurrency, reading about decentralized ledgers and Proof-of-Work can be dry.

I teach cybersecurity, and I just published "Blockchain in a Box" (iCSI Coin)—a completely free, open-source lab environment where students can spin up crypto nodes and work with the concepts. (Lesson plan docs for students are linked below if you are interested!)

Quick Install: A one-shot installer is on the right-hand side of the webpage linked below. You will need a Kali Linux or Ubuntu VM to run it.

🔗 Project & Installer: crypto.cyberlessons101.com

This one took me a while and is, at its core, a port of the Litecoin blockchain.

Hope someone out there finds this useful!

Hi all — I'm pivoting into cybersecurity and kept hearing "you need experience, not just certs." So I built a home lab of 5 working projects and open-sourced everything (MIT):

• Mini-SOC on AWS — Terraform-deployed detection stack (VPC → CloudTrail → S3 → GuardDuty → SecurityHub), 3 adversary-emulation scenarios with Stratus Red Team, triage guides + blank incident report templates
• CloudTrail IOC analyzer — Python CLI that parses CloudTrail JSON, flags anomalous logins / brute-force spikes / risky IAM changes, enriches IPs via AbuseIPDB, passing pytest suite
• Phishing analysis lab — full walkthrough of a reconstructed phish: header forensics, SPF/DKIM/DMARC, URL deobfuscation, blank analysis template, GoPhish self-test guide (own mailbox only)
• ELF binary triage — one-command static triage CLI: section-entropy packing heuristics, W^X detection, suspicious-import watchlist, score-based verdict + analyst report
• SOC agent skills — 5 MIT-licensed agent skills distilled from the projects above (alert triage, incident report, cloudtrail-ioc, phishing-analysis, binary-triage)

Everything runs on synthetic training data (clearly labeled — no real logs or real phishes). I did all the hands-on work myself: ran my own attacks, wrote my own detections and reports.

Repo: https://github.com/szzxli/soc-home-lab

If you're also building a portfolio for SOC analyst roles, happy to compare notes. And if you spot something I did wrong, tell me — that's the point of putting it in public.

Hii This is Raksha, I'm starting my journey into cybersecurity.

As a BCA graduate, my goal is clear - I want to build a career as a SOC Analyst.

It's been 10 days since I started learning fundamentals on TryHackMe, and I'm taking it slow, on purpose.

So far I've covered the basics - what cybersecurity really is, offensive vs defensive, how computers actually work, client-server, cloud & virtualization, Windows fundamentals, command line (Linux & Windows), OS security, data encoding, and the basics of Python, JavaScript, and SQL.

I know these are beginner topics. But I'm learning that you can't skip fundamentals if you want to do well in the real stuff like Networking, Wireshark, SIEM, and Incident Response.

I'll be documenting everything here - what I learn, what I get wrong, the labs I complete, and the small wins.

Not trying to rush it. Just trying to get genuinely good at it, one step at a time.

#CyberSecurity #SOCAnalyst #BCA #informationSecurity

¡Hola a todos!Estoy terminando Ingeniería en Informática y estoy desarrollando un proyecto académico llamado SecureCode.Es una herramienta que busca automatizar la evaluación de controles de seguridad en repositorios de GitHub, identificando cumplimientos e incumplimientos y generando evidencia para facilitar las revisiones.Para complementar el proyecto, necesito conocer la opinión de estudiantes, desarrolladores y profesionales del área TI sobre la utilidad de este tipo de soluciones.No necesitan ser expertos en ciberseguridad ni haber utilizado SecureCode. La encuesta incluye una explicación del proyecto.⏱️ Duración: 5–7 minutos.

🔒 Anónima y voluntaria.

🎓 Finalidad exclusivamente académica.

💻 Dirigida a estudiantes y profesionales del área informática.Enlace a la encuesta: https://docs.google.com/forms/d/e/1FAIpQLSeiHEDD-ZIwY7WvqOXYJi8dAmAR4E44sejHmlwhqCa3JkExFg/viewform?usp=header

usp=header ayudarían muchísimo respondiendo. También agradecería cualquier comentario o sugerencia sobre el proyecto.¡Muchas gracias por su tiempo!

Our risk trend line has declined for eight quarters and it would have declined the same way if we had done absolutely nothing, which is a thing i worked out about a year ago and have been sitting on since.

The number stopped responding to the work. Close four hundred findings in a quarter and it does the same thing as closing none, so at some point it stopped being a measure of the programme and became decoration.

What i have is a choice. A number that keeps improving, which the board likes and nobody has asked me to explain, or a number i could defend under questioning, which is worse and invites the follow up about why it got worse under me.

I am not saying its dishonest, its just answering a narrower question than everybody in that room assumes.

I stopped believing it about a year ago and kept presenting it, which is the part i find interesting about myself.

Nobody has asked how its calculated yet. I am not volunteering.

How are you building a risk number the board can actually interrogate.

I built a free agent protocol inspector tool that can provide IGA style review packets for security teams looking to review Agent access. It looks into MCP, A2A, ARD & poppy.json to provide a comprehensive picture.

Here is the link: https://contextiq.trango-compute.com/dashboard/agent-protocol-inspector