Skip to main content
Sandfish

JOIN-Banco Azteca

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

Group896c2395-2ac2-4ef6-9b73-a3f806bbdab7submitted urlMember 1

Results

Rules engine

AI review

AI case description

Phishing

The page presents a Banco Azteca-branded username and password form, and its submission sends the credentials to a separate procesos-eficientes.com domain on port 63105. The evidence does not establish that this flow is authorized or that the credentials were misused.

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
46.0s
Navigation
3 navigations
Engine version
0.4.2
Created
2026-11-21 22:16:53Z
Started
2026-11-21 22:16:54Z
Finished
2026-11-21 22:17:40Z
Archive
436 KB
Favicon source
html_link / favicon-v7
Analysis ID
bbc612de-d938...

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.

NavigationBrowser-observed HTTP statusRecorded requests
0200Inspect navigation 0 requests
1200Inspect navigation 1 requests
2200Inspect navigation 2 requests
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