j0moz4@LIITN:/web:$'s blogKeramon

Tags · offensive-security

h0me

c0nt3nt

ad/lab-(bleach.local)

w4ke-up-s4mura1

komm4nds-ch347-sheet

x$$-f0r3st

de4l3r

5elgfingerprintingjavascriptred-teamxssdealersphishingoffensive-securityproxy-injectionpowershellbashcallback

Offensive Callback (II): Dealers — Collection Points and Routing Engine

Second post in the Offensive Callback series. This one is about dealers: the server-side collection endpoints that define what happens when a request arrives and how telemetry gets delivered back. If you haven’t read the first post about the server architecture, start there. Here I’m going to focus entirely on the dealer system. What is a dealerA dealer i..

Read more
5elgfingerprintingred-teamnodejsoffensive-securitywebsocketcallback-serverhttpdnsicmpexfiltrationsqlitecss-tracking

Offensive Callback: Multi-Protocol Passive Intelligence Collection

So I’ve been sitting on this for a while. I’ve been working on a tool that I call Offensive Callback — a passive intelligence collection server that captures inbound traffic across HTTP(S), WebSocket, DNS, and ICMP simultaneously, enriching every hit with browser telemetry, geolocation, and automated OSINT. This post is about the server itself: what it ru..

Read more
loading..
tracking5elgfingerprintingbrowserjavascriptred-teamxssdealersphishingoffensive-securityproxy

5ELG (I)/ Dealers wanna deal

In our previous post, we introduced 5ELG (https://github.com/jomoza/5ELG)This open-source project, with its modular “merca” (client-side) and “dealer” (server-side) components, offers a robust approach to tracking, data collection, and live monitoring, all within a customizable and scalable framework. Today, we’ll take a closer look at the full potential ..

Read more