C:\users\rideckszz\profile_ □ ×

@rideckszz / organizer

Derick G. Andrighetti

Cybersecurity student, technical writer, CTF organizer, and exploitCamp maintainer interested in offensive security, software security, SDN, and self-protecting networks.

exploitCampoffensive securitytechnical writing

profile.json

{
"name": "Derick G. Andrighetti",
"handle": "rideckszz",
"role": "organizer",
}
About
C:\>whoami_ □ ×

About me

I study and work around cybersecurity with a focus on offensive security, secure software, and practical learning environments.

My work connects CTFs, technical writing, security education, and research on self-protecting networks.

Security

I am interested in offensive security, vulnerability analysis, exploitation workflows, and defensive reasoning.

Research

I research cybersecurity and self-protecting networks, with interest in SDN, adaptation, and network protection.

Education

I create material for security learning, CTF practice, and technical onboarding.

exploitCamp
C:\>community_ □ ×

What I do here

In exploitCamp, I help organize learning content and practical security activities for people who want to understand exploitation without skipping fundamentals.

Content

Introductory materials about web security, exploitation, enumeration, SQL Injection, privilege escalation, and CTF methodology.

CTFs

Challenges and guided practice designed to help beginners connect theory, tooling, and reasoning.

Writing

Technical notes that prioritize clarity, reproducibility, and safe practice in authorized environments.

Community

Support for building a stronger cybersecurity culture through study groups, practical labs, and shared learning.

Focus: learn the behavior of systems before relying on tools.

Interests
C:\>topics_ □ ×

Main areas

Offensive Security

Enumeration, exploitation, web vulnerabilities, privilege escalation, CTF methodology, and practical labs.

SDN

Software-defined networks, Mininet, ONOS, traffic analysis, and mitigation strategies.

Self-protecting Networks

Adaptive systems that can detect, reason about, and react to security events.

Automation

Scripts and tooling to reduce repetitive work, organize security testing, and document results.

Technical Writing

Security materials, tutorials, walkthroughs, and structured documentation for learning.

CTFs

Challenges, study groups, labs, and exercises focused on applied reasoning.

Toolbox
C:\>stack_ □ ×

Languages and tools

These are tools and technologies I use or study across security, development, research, and infrastructure.

Backend

Python, Java, C, C++, C#, Django, Bash, Lua, JavaScript.

Frontend

HTML, CSS, React, TypeScript, and interface prototyping.

Security

Linux, Burp Suite, Nmap, ffuf, Gobuster, Metasploit, Frida, CTF labs, and custom scripts.

Infrastructure

Docker, Kubernetes, Nginx, Cloudflare, AWS, Azure, and Linux servers.

Research Lab

Mininet, ONOS, Open vSwitch, SDN controllers, traffic simulation, and network experiments.

Workflow

GitHub, VS Code, Figma, Notion, technical notes, and reproducible documentation.

Current focus
C:\>now_ □ ×

What I am building

exploitCamp materials

Writing beginner-friendly content about web security, exploitation, privilege escalation, and CTF practice.

Security training

Creating practical material that connects vulnerabilities, threats, tools, and developer guidance.

SDN security

Studying self-protecting networks and mitigation strategies for attacks in software-defined environments.

Technical portfolio

Publishing structured notes, labs, and educational resources for cybersecurity learners.

I like building material that turns vague security topics into concrete workflows people can reproduce safely.

Learning philosophy
C:\>method_ □ ×

Understand before automating

My approach to security learning is based on understanding the system before using the tool.

Observe

Start by understanding normal behavior: services, inputs, responses, permissions, and assumptions.

Hypothesize

Build a testable idea about where the weakness might be.

Validate

Use tools to confirm or reject the hypothesis instead of running random payloads.

Document

Record what worked, what failed, and why the result matters.

Links
C:\>contact_ □ ×

Find me online

You can find my public projects, technical notes, and contact channels here:

GitHubLinkedInTwitterEmail
github   -> https://github.com/rideckszz
linkedin -> https://www.linkedin.com/in/derick-andrighetti/
twitter  -> https://twitter.com/rideckszz
email    -> derickcollege@gmail.com
write-ups
official

SimpleCTF

Write-up oficial do SimpleCTF, com enumeração, exploração de CMS vulnerável, acesso SSH e Linux privesc.

SimpleCTF • web • official