English

I will admit, as this is my personal blog, that I’m not the biggest LLM fan. I do not believe the hype that this is going to further revolutionize cybersecurity in the sense that I think it has furthered automation and that’s it, to me, that’s not really a praxis change. However as a hacker I also believe it is important to adapt to tools and help in understanding how they can be attacked, and its adoption is undeniable. Please do not take this as the naive view of “AI is not THAT important”, but as a (I hope) informed bias disclosure for whomever it may concern. ...

This is a Vulnyx VM. As usual lets begin with basic discovery: Arpsweep: sudo nmap -sn 192.168.56.100/24 -oN arpsweep.txt [sudo] password for kali: Starting Nmap 7.95 ( https://nmap.org ) at 2025-04-01 20:10 CEST Nmap scan report for 192.168.56.1 Host is up (0.00014s latency). MAC Address: 0A:00:27:00:00:00 (Unknown) Nmap scan report for 192.168.56.10 Host is up (0.00020s latency). MAC Address: 08:00:27:E9:B5:FB (PCS Systemtechnik/Oracle VirtualBox virtual NIC) Nmap scan report for 192.168.56.111 Host is up (0.00082s latency). MAC Address: 08:00:27:2B:FF:06 (PCS Systemtechnik/Oracle VirtualBox virtual NIC) Nmap scan report for 192.168.56.100 Host is up. Nmap done: 256 IP addresses (4 hosts up) scanned in 2.19 seconds So target IP is 56.111 ...

Let’s start with an arpsweep to discover the targets IP address: sudo nmap -sn 192.168.56.100/24 -oN arpsweep.txt Which results as: Starting Nmap 7.95 ( https://nmap.org ) at 2025-04-01 18:47 CEST Nmap scan report for 192.168.56.1 Host is up (0.00021s latency). MAC Address: 0A:00:27:00:00:00 (Unknown) Nmap scan report for 192.168.56.10 Host is up (0.00020s latency). MAC Address: 08:00:27:E9:B5:FB (PCS Systemtechnik/Oracle VirtualBox virtual NIC) Nmap scan report for 192.168.56.110 Host is up (0.00042s latency). MAC Address: 08:00:27:DE:0D:24 (PCS Systemtechnik/Oracle VirtualBox virtual NIC) Nmap scan report for 192.168.56.100 Host is up. Nmap done: 256 IP addresses (4 hosts up) scanned in 2.15 seconds Target is 56.110 ...

Ping for TTL and visibility ❯ ping -c 1 10.10.10.245 PING 10.10.10.245 (10.10.10.245) 56(84) bytes of data. 64 bytes from 10.10.10.245: icmp_seq=1 ttl=63 time=37.3 ms --- 10.10.10.245 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 37.252/37.252/37.252/0.000 ms (TTL suggests Linux) ❯ sudo nmap -sS -A -T4 10.10.10.245 -oN nmap.txt [sudo] password for kali: Starting Nmap 7.95 ( https://nmap.org ) at 2025-02-18 19:30 CET Nmap scan report for 10.10.10.245 Host is up (0.037s latency). Not shown: 997 closed tcp ports (reset) PORT STATE SERVICE VERSION 21/tcp open ftp vsftpd 3.0.3 22/tcp open ssh OpenSSH 8.2p1 Ubuntu 4ubuntu0.2 (Ubuntu Linux; protocol 2.0) | ssh-hostkey: | 3072 fa:80:a9:b2:ca:3b:88:69:a4:28:9e:39:0d:27:d5:75 (RSA) | 256 96:d8:f8:e3:e8:f7:71:36:c5:49:d5:9d:b6:a4:c9:0c (ECDSA) |_ 256 3f:d0:ff:91:eb:3b:f6:e1:9f:2e:8d:de:b3:de:b2:18 (ED25519) 80/tcp open http Gunicorn |_http-server-header: gunicorn |_http-title: Security Dashboard Device type: general purpose Running: Linux 5.X OS CPE: cpe:/o:linux:linux_kernel:5.0 OS details: Linux 5.0, Linux 5.0 - 5.14 Network Distance: 2 hops Service Info: OSs: Unix, Linux; CPE: cpe:/o:linux:linux_kernel TRACEROUTE (using port 111/tcp) HOP RTT ADDRESS 1 37.88 ms 10.10.14.1 2 38.07 ms 10.10.10.245 OS and Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 18.76 seconds FTP Enum No FTP anon login allowed sadly: ...

Hello there, this is mostly a test post to get a visual on how hugo works. Using .toml files for content management is looking awesome so far.