Detailed analysis of captured phishing page
Used to detect similar phishing pages based on HTML content
| Algorithm | Hash Value |
|---|---|
|
CONTENT
TLSH
|
T15DC15060E424DD338353D6E1BBA49B0A72D8C347CA46450866F8536E6FE3DD5CE261A1 |
|
CONTENT
ssdeep
|
96:11RrAPn8G36sgCD6sTUxSNgEj6sTzX1p6sIGUJvySOzrG4vSAKyFSAb3+3pxRHUR:al9D+cVPpYgDS3RHAN3/ |
Used to detect visually similar phishing pages based on screenshots
| Algorithm | Hash Value |
|---|---|
|
VISUAL
pHash
|
989973674c5932dc |
|
VISUAL
aHash
|
ffff3e1818000000 |
|
VISUAL
dHash
|
f0f8f0b2b2f1dab0 |
|
VISUAL
wHash
|
ffffff1c180c0800 |
|
VISUAL
colorHash
|
1bc00010000 |
|
VISUAL
cropResistant
|
e0e0f0f0c0e0c0c1,f0f8f0b2b2f1dab0 |
• Amenaza: Phishing de credenciales
• Objetivo: Usuarios de Microsoft
• Método: Suplantación a través de una página de inicio de sesión falsa.
• Exfil: Desconocido, pero se detectaron formularios (probablemente recolectando credenciales).
• Indicadores: Coincidencia de dominio, formulario que solicita información sensible.
• Riesgo: Alto
The attacker attempts to steal user credentials by mimicking a legitimate login page. Users are prompted to enter their Microsoft account information on the fake page, which is then captured by the attacker.
The JavaScript code is obfuscated to make it difficult to analyze and detect malicious activity.
1. Step 1: Victim visits URL with 'urid' parameter (victim identifier) 2. Step 2: Script initializes and extracts URL parameters (urid, rid, cid, uid) 3. Step 3: Script tracks all user interactions (keystrokes, clicks, form submissions) via event listeners 4. Step 4: For each interaction, sendData() exfiltrates data to C2 via 'getresponse.getmainpoint' with custom headers 5. Step 5: getMessageData() fetches dynamic phishing content based on interaction type (e.g., type 5 for form submissions) 6. Step 6: crajsonpcallback() injects fetched content into DOM (#omContent) 7. Step 7: If AJAX fails, addTrackerImage() sends data via 1x1 pixel image 8. Step 8: On successful exfiltration, server may respond with redirect URL (window.location.replace) 9. Step 9: Conditional alerts/modals shown based on server responses (e.g., fake training links, company names)
1. Step 1: Victim visits URL with 'urid' parameter (victim identifier) 2. Step 2: Script initializes and extracts URL parameters (urid, rid, cid, uid) 3. Step 3: Script tracks all user interactions (keystrokes, clicks, form submissions) via event listeners 4. Step 4: For each interaction, sendData() exfiltrates data to C2 via 'getresponse.getmainpoint' with custom headers 5. Step 5: getMessageData() fetches dynamic phishing content based on interaction type (e.g., type 5 for form submissions) 6. Step 6: crajsonpcallback() injects fetched content into DOM (#omContent) 7. Step 7: If AJAX fails, addTrackerImage() sends data via 1x1 pixel image 8. Step 8: On successful exfiltration, server may respond with redirect URL (window.location.replace) 9. Step 9: Conditional alerts/modals shown based on server responses (e.g., fake training links, company names)
reporter_v8.jssendData()postData()getMessageData()crajsonpcallback()reshapeCode()unMinifyUrl()addTrackerImage()Pages with identical visual appearance (based on perceptual hash)
Found 2 other scans for this domain