prodba[.]vercel[.]app

prodba.vercel.app is a tenant hostname on Vercel, not a separately registered domain. PhishDestroy first recorded this hostname on Feb 26, 2026. The assembled evidence scores 100/100 (critical).

Three independent sources are positive: VirusTotal, Google Safe Browsing, and Cloudflare Radar. VirusTotal recorded 14 detections among 93 engines: ADMINUSLabs, Criminal IP, alphaMountain.ai, BitDefender, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safebrowsing, Kaspersky, Lionic, Sophos, VIPRE, Webroot on Jul 18, 2026 at 20:45 UTC. Google Safe Browsing flagged the domain: Social Engineering on Mar 2, 2026 at 20:51 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories phishing and security threats; its verdict timestamp was not retained. The evidence is not unanimous. The external blocklist snapshot contained no matches on Aug 7, 2026 at 18:20 UTC. URLQuery recorded no positive detection. URLScan completed without a malicious verdict (score 0) on Mar 25, 2026 at 12:13 UTC.

HTTP 451 (Unavailable for Legal Reasons) was recorded on Aug 7, 2026 at 01:30 UTC. Vercel is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 216.198.79.67 on AS16509 (AMAZON-02 - Amazon.com, Inc., US). The associated network metadata labels the endpoint as AS16509 Amazon.com, Inc. in Walnut, US. This is shared platform infrastructure; the IP and ASN are hosting context, not attribution to unrelated tenants. The stored server header is Vercel. Captured page title: “Deployment Unavailable”. DOM analysis completed on Jul 29, 2026 at 04:10 UTC; stored DOM score 100/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. IoC extraction completed on Aug 1, 2026 at 04:27 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators. The platform TLS certificate was issued by Google Trust Services / WR1 with validity through May 27, 2026; checked Mar 15, 2026 at 08:10 UTC.

No target brand has been confirmed from stored page content; hostname wording alone is not treated as brand evidence. Taken together, the page content and independent findings support classifying this hostname as phishing. The stored record does not establish the post-click interaction, and it does not claim a confirmed wallet-draining transaction or credential submission.