Detailed analysis of captured phishing page
Used to detect similar phishing pages based on HTML content
| Algorithm | Hash Value |
|---|---|
|
CONTENT
TLSH
|
T108D22EB09156AA3B02F392E1AB752B6FB3D5E2C8D94307052AFCC75D4FCEE94E921051 |
|
CONTENT
ssdeep
|
384:cL3Ubc+VW8Cvq87CygUyD084mR8m9Q8lzK:cLmc+VDCC1WQ8yVK |
Used to detect visually similar phishing pages based on screenshots
| Algorithm | Hash Value |
|---|---|
|
VISUAL
pHash
|
868e93f1f1e1a88e |
|
VISUAL
aHash
|
ff14102038002020 |
|
VISUAL
dHash
|
4c6d655270444840 |
|
VISUAL
wHash
|
ff0410bb3c3c2c2c |
|
VISUAL
colorHash
|
0f000000e00 |
|
VISUAL
cropResistant
|
4c6d655270444840 |
• Amenaza: Phishing por suplantación
• Objetivo: Usuarios de bet365
• Método: Suplantación de dominio con mímica visual
• Exfil: /login_action
• Indicadores: Coincidencia de dominio, ofuscación, acciones de formulario
• Riesgo: Alto
The attacker is attempting to steal user credentials by creating a fake login page that closely resembles the legitimate bet365 website. Users entering their username and password will have their credentials stolen.
1. Step 1: User lands on phishing page and fills out registration/login form (fields: userid, password1, confirmpassword1, realname, tel, email, question, answer)
2. Step 2: Form validation functions (e.g., checkPassword, checkEmail) execute client-side checks to mimic legitimacy
3. Step 3: On submission, $('#btnSubmit').click() triggers AJAX POST to /getcode with affiliate code or other data
4. Step 4: For login forms, encrypted credentials are sent via $.post('/login_action') using JSEncrypt to obfuscate payloads
5. Step 5: Server processes data (e.g., stores credentials, triggers secondary actions like fake 'success' alerts or redirects)
6. Step 6: Decoy functionality (e.g., playgame_modal) may distract users or deliver additional payloads
1. Step 1: User lands on phishing page and fills out registration/login form (fields: userid, password1, confirmpassword1, realname, tel, email, question, answer)
2. Step 2: Form validation functions (e.g., checkPassword, checkEmail) execute client-side checks to mimic legitimacy
3. Step 3: On submission, $('#btnSubmit').click() triggers AJAX POST to /getcode with affiliate code or other data
4. Step 4: For login forms, encrypted credentials are sent via $.post('/login_action') using JSEncrypt to obfuscate payloads
5. Step 5: Server processes data (e.g., stores credentials, triggers secondary actions like fake 'success' alerts or redirects)
6. Step 6: Decoy functionality (e.g., playgame_modal) may distract users or deliver additional payloads
encforms.js (handles encrypted form submission) and checkinput.js (contains credential validation logic)checkPassword()checkConfirmPassword()getcode()$('#btnSubmit').click()$.ajax() and $.post() calls in form submission handlersplaygame_modal() (likely a decoy or secondary payload delivery mechanism)Pages with identical visual appearance (based on perceptual hash)
Found 10 other scans for this domain