Skip to main content
Sandfish

JOIN-Banco Azteca

https://bancoazteca.procesos-eficientes.com:63105/Aware…

Group8b03e524-76b1-4959-9c4f-251a032435ecsubmitted urlMember 1

Results

Rules engine

AI review

AI case description

Phishing

The page presents a Banco Azteca-branded username/password login on an Azure-hosted domain and submits credentials to a separate domain, procesos-eficientes.com, which also supplies the page’s assets. This supports cross-domain credential flow and brand impersonation, but the evidence does not establish whether that separate domain is an authorized service or an abusive collector.

Findings

Analyzed page

Language
Detecting...

Infrastructure

Domain registration
azurewebsites.netMore than 90 days oldRegistered 2012-01-24 · Registrar MarkMonitor Inc.
Hosting
Loading...

Capture activity

Cookies
9 observed
Interaction
8 actions · 2 submissions · stopped: repeated state · download stage: no payload control
  1. 1. fillsucceededtext | userName | Username Testing Mode: | Username
  2. 2. fillsucceededpassword | password | Password | Password
  3. 3. submitsucceededEntrar
  4. 4. fillsucceededtext | userName | Username Testing Mode: | Username
  5. 5. fillsucceededpassword | password | Password | Password
  6. 6. submitsucceededEntrar
  7. 7. validationobservedValidation (valueMissing) | text | userName | Username Testing Mode:
  8. 8. validationobservedValidation (valueMissing) | password | password | Password
Kit source work

Loading related source work…

Discover or upload kit source

Analysis metadata

How and when the analysis ran.

Processing status
Evidence coverage
Input kind
url
Execution kind
capture
Duration
29.0s
Navigation
4 navigations
Engine version
0.4.2
Created
2026-11-21 02:03:44Z
Started
2026-11-21 02:03:45Z
Finished
2026-11-21 02:04:14Z
Archive
436 KB
Favicon source
html_link / favicon-v7
Analysis ID
e0b5f4c8-3c68...

Document-source diagnostics

These records identify rejected document reads. A current epoch does not prove that a replacement read succeeded. Later success does not erase an earlier evidence limit.

No rejected document reads were recorded.

Browser-observed navigation status

The browser status can differ from the normalized origin response, including during a proxy failure. Inspect the recorded document request for origin response evidence.

Showing 0–0 of 0

Signals by severity

Detected findings grouped by risk

Request activity

Network requests grouped by resource type

Behavior

Recorded actions grouped by type

Network contacts

Requests to the most active hosts

Request ownership

First-party and third-party requests

Response MIME types

Network responses grouped by MIME type