Posts

Showing posts from October, 2026

Analysis of Telegram 1500 NGN Task Scam Impersonating Content Creator "Roxanne"

Image
Fig 1: Live evidence - Unsolicited Telegram DM promising 1500 NGN for screenshot task. Red flags: gibberish username, unrealistic daily earnings, PII request. Lab 07: Telegram 1500 NGN Task Scam — SOC Analysis Incident Date: 27 Oct 2026 Platform: Telegram Threat Actor: Vfddgg Vgdddf (Claims "Roxanne - Content Creator") Analyst: Roland Benjamin | NOC Engineer (MTN) | Aspiring SOC Analyst ⚠️ Alert Summary: Unsolicited Telegram DM promising 1500 NGN for screenshot task, claiming 50k-160k per day earnings. 1. Evidence "Okay just to explore and take a screenshot of our Video we pay 1500 naira for it earning is up to 50,000 to 160,000 per day is possible... Before we continue, could you tell me your age?" 2. SOC Triage - 5 Red Flags Unsolicited Contact: Random account "Vfddgg Vgdddf" - no mutuals, gibberish name. Unrealistic Pay: 1500 NGN for 2 mins = Too Good To Be True. Real jobs don't pay 160k/day for screenshots. PII Harvesti...

Lab05: How I Detect Phishing URLs in 3 Checks | Phishing Detector Tool

Image
 How SOC Analysts Catch Phishing Links Phishing is MITRE T1566. I built a detector that checks URLs before you click. Test URL: http://secure-login-paypal.com (fake lab example) [CHECK] Domain age: 2 days -> SUSPICIOUS (real PayPal is 20+ years) [CHECK] SSL: Invalid -> SUSPICIOUS [CHECK] Keywords: secure-login + paypal -> PHISHING (brand impersonation) [ALERT] PHISHING SCORE: 95% - BLOCK THIS URL [MITRE] T1566 Phishing - Credential Harvesting 3 checks every SOC analyst does: 1. Domain age - New domains are risky 2. SSL cert - No HTTPS = danger 3. Keywords - secure-login-paypal is classic phishing trick I wrote phishing_detector.py on iPhone. It could save someone from losing their account. Next: Lab06 will be IP Blocker automation. Disclaimer: URL used is a synthetic lab example, not a live phishing site. For defensive education only.

Lab04: I Built a SOC Log Analyzer in Python That Scores Threats | Python SOC Tool

Image
 How SOC Analysts Automate Log Analysis Reading 1,000+ log lines manually is impossible. So I built log_parser.py on my iPhone. What it does: Parsing 1,245 lines from auth.log... [FOUND] 12 Failed logins -> IP 192.168.1.15 [FOUND] 3 Root login attempts -> ALERT [FOUND] 8 Port scan pattern -> MITRE T1046 [RESULT] Threat Score: 85/100 - HIGH [ACTION] Report generated: soc_report_27Oct.txt This is how real SOC tools work. They parse logs, find patterns, and give a threat score. My Python logic: - Count failed logins per IP - Detect root attempts (privilege escalation) - Detect port scan patterns (MITRE T1046) - Generate auto report Built entirely in iSH on iPhone. No laptop. Lesson: Automation is what separates Junior SOC from Senior SOC. Disclaimer: Lab uses private lab logs (192.168.1.15). Defensive only.

Lab01: No Laptop? No Problem. How I Built a $0 SOC Lab on iPhone

Image
 How I Started My SOC Journey With Just an iPhone Everyone told me you need a laptop to learn cybersecurity. I didn't have one. All I had was my iPhone and data. So I built a full SOC lab on my iPhone for $0. What I Used: 1. iSH App - It gives you Linux Alpine on iPhone. Free on App Store. 2. Python 3.11 - Already inside iSH 3. Blogger - For documenting my labs (this blog) My Setup Commands (see terminal image above): uname -a -> Shows Linux iPhone 6.0.0-ish Alpine - Yes, Linux on iPhone! python3 --version -> Python 3.11.6 ready ls ~/soc-lab/ -> My lab folder: scanner.py, logs/, rules/ echo "No Laptop? No Problem." -> My mindset. Why This Matters for SOC: A SOC Analyst doesn't need expensive tools. We need to understand logs, detection, and defense. I can run Python port scanners, parse logs, and write detection rules all from my phone. Cost of my lab: $0 What I learned: Priceless. If you have a phone, you can start today. Don't wait for a laptop. In L...

Lab02: How SOC Analysts Detect Brute Force Attacks in 60 Seconds

Image
 What is a Brute Force Attack? A Simple SOC Explanation A brute force attack is when an attacker tries many passwords quickly to guess your login. As a SOC analyst, your job is to spot this pattern early. In this lab, I simulated failed logins on my local lab (127.0.0.1) to show how we detect it. Step 1: View Authentication Logs In Linux, failed logins are stored in /var/log/auth.log. We can filter for failures: cat /var/log/auth.log | grep Failed This command shows lines like: Failed password for admin from 192.168.1.15 port 5321 Step 2: Spot the Attack Pattern A normal user fails 1-2 times. An attacker fails 5, 10, 20 times in 60 seconds from the SAME IP. In my lab simulation (see terminal image above): 5 failed logins from 192.168.1.15 in 60 seconds That IP is scanning common usernames: admin, root. Step 3: The Defensive Rule In a real SOC, we create a detection rule: If >5 failed logins from one IP in 60 seconds Then: Block IP + Alert SOC This is MITRE ATT&CK Technique T...

How I Built an Ethical TCP Port Scanner on iPhone for SOC Detection | Lab03

Image
 How I Built an Ethical TCP Port Scanner on iPhone to Think Like an Attacker (and Defend Better) — Lab03 As a SOC Analyst learner, I made a mistake. I was only learning defense — logs, alerts, IOCs. But I couldn't understand WHY the SIEM was firing "Port Scan Detected" alerts. So I decided: To be a better defender, I must think like an attacker. This week, I built Lab03 of my SOC Toolkit — a TCP Port Scanner — entirely on my iPhone using iSH. And it taught me more about SOC detection than any course. What is a Port Scanner and Why Should SOC Analysts Care? A port scanner is the first tool hackers use. Before they exploit anything, they check which doors are open. Common ports they look for:  •  Port 22 = SSH (to brute-force login)  •  Port 3389 = RDP (to take over Windows)  •  Port 80 / 443 = Web servers  •  Port 445 = SMB (for ransomware) In MITRE ATT&CK framework, this is TA0043 - Reconnaissance. If you see it in your SIEM, you are in S...