Julian X.
Mexico City, Mexico · Cyber Security Analyst · PEKXEL
36 followers
About
Cybersecurity analyst with a strong software engineering background, specializing in incident investigation, threat detection, and log analysis. Experienced in investigating web, network, and malware attacks using frameworks like MITRE ATT&CK and NIST.
Skills
- Splunk
- Wireshark
- TCP/IP
- Suricata
- Sysmon
- Python
- Bash
- Nmap
- Metasploit
- Burp Suite
32 skills in total
Licenses & Certifications
-
Python for Cybersecurity
INFOSEC
Issued Jul 2025
-
Sustainable Testing With Typescript
Software Crafters Academy
Issued Feb 2024
-
Advanced Python Scripting for Cybersecurity
INFOSEC
Issued Jul 2025
6 certifications in total
Experience
-
Full Stack Web Developer
PEKXEL
Jan 2020 — Present
Puebla, México
-
Full Stack Web Developer
Contacto Mundial
Jan 2016 — Jan 2020
Puebla, México
Recent posts
🐍 Learning Python through a cybersecurity lens. Now that you know how to interact with Python through the console, it's time to learn how to make your output more readable and organized to create cleaner, more visually appealing reports.
https://jjeuribe.github.io/posts/python-for-cybersecurity-formatting-console-output/
🐍Learning Python through a cybersecurity lens. In this article, we explore another fundamental yet often-overlooked aspect of building useful security tools: console input and output. https://jjeuribe.github.io/posts/python-for-cybersecurity-console-input-and-output/
🐍Learning Python through a cybersecurity lens. In this article, we start with one of the fundamentals: variables.
https://jjeuribe.github.io/posts/python-for-cybersecurity-understanding-variables/
In this final challenge, you’re given an AWS access key with limited (mostly read-only) permissions. No admin powers, no obvious misconfigurations, this time just pure old-school enumeration.
Your job is to explore the account, follow the clues, and pay attention to the details. The more you dig, the more patterns will start to show up. Observation will be your most powerful weapon here. Alright, enough talk, here’s the challenge https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-6-when-the-gateway-finally-falls/
In this level, you’ll deal with a proxy feature that’s letting an attacker to fetch external resources on behalf of one of your EC2 instances. This may not look dangerous at first, but under the hood it opens the door to a very well-known vulnerability. https://jjeuribe.github.io/posts/aws-pentesting-flaws-level-5-exploiting-aws-imds-via-ssrf/