Skip to security report
Domain security and threat intelligence
uat.base.bh.edu.pk favicon

uat.base.bh.edu.pk

In short

uat.base.bh.edu.pk is a Base impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (78/100). Status: Last known active. Hosting: GOOGLE-CLOUD-PLATFORM - Google LLC, US. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.

“BSS Timetable”

Resolved IP
34.65.68.235
Registered
Mar 23, 2014
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 4/92 Stored blocklist matches: 2 Automated brand label: Base
Oct 11, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 4. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 4 / 92 5 sources

VirusTotal

4 / 92 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
4 / 92
Page captures
6

PhishDestroy threat report

Overview

uat.base.bh.edu.pk is a subdomain under a Pakistani educational domain that PhishDestroy classifies as an impersonation phishing page. The page presents itself as "BSS Timetable," a school-scheduling title, while our classification places it among pages that imitate a trusted service to deceive visitors. PhishDestroy first saw it on 2026-10-11, and as of 2026-10-19 the site was still online and serving live content.

How the scam works

Impersonation pages borrow the look or name of something familiar so visitors lower their guard. They then ask for a login, personal details, or, on crypto-focused variants, a wallet connection or signature. Whatever is entered goes to the operator, who can use it to take over accounts or move assets. The title reads "BSS Timetable," a school schedule, while our classification is impersonation phishing.

Evidence

On 2026-10-16, 4 of 92 VirusTotal engines flagged the site: alphaMountain.ai, CRDF, Forcepoint ThreatSeeker and SOCRadar. That is a low count, but these vendors reached the verdict independently. The stronger signal is the blocklist coverage. Besides PhishDestroy, the site is listed by MetaMask and SEAL, two wallet-security lists, which shows the crypto community regards it as a risk to wallet users.

Infrastructure

The parent domain was registered on 2014-03-23, more than twelve years before PhishDestroy detected this subdomain. An old institutional domain carries borrowed trust that a newly registered domain would not have. The site runs on Google Cloud Platform infrastructure, on an address located in Switzerland. It uses a free Let's Encrypt certificate, so the padlock in the browser says nothing about whether the site is legitimate.

What to do

If you entered a password here, change it now, along with any account that shares it, and turn on two-factor authentication. If you connected a crypto wallet or signed anything on this page, revoke the permissions you granted with a token-approval checker. Move any remaining funds to a fresh wallet if you exposed a seed phrase. Defenders should block the subdomain at the DNS and proxy level and check logs for visits since 2026-10-11. Report the page to the hosting provider and to the administrators of the parent educational domain so they can secure it.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

URLScan · 2026-10-11T11:27:00Z

Observed: · Retrieved:

Uuid
01a12ab7-403a-77d8-a4ec-42a3e487837c
Final url
https://uat.base.bh.edu.pk/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://uat.base.bh.edu.pk/",
        "from": "http://uat.base.bh.edu.pk/",
        "status": 307
    }
]
Ip
34.65.68.235
Ptr
235.68.65.34.bc.googleusercontent.com
Contacted domains
[
    "accounts.google.com",
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "142.251.127.84",
    "104.17.25.14",
    "34.65.68.235"
]
Asns
[
    "15169",
    "13335",
    "396982"
]
Countries
[
    "US",
    "CH"
]
Document hash
ff5bddfaf8937472d3402ffd0437ead25317f543b15d1aaa7a94c06d8a5f0747
Script hashes
[
    "015c3bc62fce425cc5d2fdd153205454f568c3de0511ea83af5114df35a40a7a"
]
Globals
[
    "$",
    "jQuery",
    "__reactRouterVersion",
    "default_gsi",
    "_F_toggles_default_gsi",
    "google",
    "__G_ID_CLIENT__",
    "closure_lm_933080"
]
Cookies
[
    "g_state"
]
Storage keys
[
    "__sak"
]
Tls
{
    "san": [
        "api.base.bh.edu.pk",
        "prototype.base.bh.edu.pk",
        "staging.base.bh.edu.pk",
        "uat.base.bh.edu.pk"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR2",
    "subject": "api.base.bh.edu.pk",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-08T06:08:22Z",
    "valid_from": "2026-09-09T06:08:23Z"
}
Domain age days
937
Apex age days
2034
Tls age days
32
Tls valid days
89
Requests
16
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -15,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Apache/2.4.52 (Ubuntu)",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-12T10:16:11Z

Observed: · Retrieved:

Uuid
5a3ef46d-ffa0-4244-a5eb-d453d6f5e269
Final url
https://uat.base.bh.edu.pk/
Status
200
History
[
    {
        "url": "https://uat.base.bh.edu.pk/",
        "status": 200
    }
]
DOM structure hash
c3f52297740dfde188023fc70548662e8eaca9f7685adc5ca3dd51da9724a9b1
Document hash
ff5bddfaf8937472d3402ffd0437ead25317f543b15d1aaa7a94c06d8a5f0747
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "uat.base.bh.edu.pk",
        "type": "A",
        "value": "34.65.68.235"
    }
]
Dnssec valid
false
Ip
34.65.68.235
Registration record
{
    "created": "2014-03-23T00:00:00Z",
    "expires": "2032-03-23T00:00:00Z",
    "nameservers": [
        "cruz.ns.cloudflare.com",
        "nile.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-20T02:00:15Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 1,
    "undetected": 35
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "suspicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "educational institutions",
    "alphaMountain.ai": "Education, Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Created
2014-03-23T00:00:00Z
First seen
2024-07-16T15:09:46Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "34.65.68.235"
    }
]
Dns at
2026-10-20T02:00:31Z
Jarm
15d3fd16d29d29d00042d43d000000ad5982e0c23bdf2bdf34e47480ccc0a3
Certificate
{
    "san": [
        "api.base.bh.edu.pk",
        "prototype.base.bh.edu.pk",
        "staging.base.bh.edu.pk",
        "uat.base.bh.edu.pk"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "57f3fc3f7cb836e9a17b19447bb526dee5f",
    "sha256": "05632030b3c35c8fd3fa7fc52a7b171fc3ce4ed814ab020edc3f7443c769eee0",
    "subject": "api.base.bh.edu.pk",
    "valid_to": "2026-12-08T06:08:22Z",
    "valid_from": "2026-09-09T06:08:23Z"
}
Registration record
{
    "created": "2014-03-23T00:00:00Z",
    "nameservers": [
        "cruz.ns.cloudflare.com",
        "nile.ns.cloudflare.com"
    ]
}

Questions about uat.base.bh.edu.pk

Is uat.base.bh.edu.pk legit?

No. PhishDestroy classifies uat.base.bh.edu.pk as a Base impersonation page (risk: critical, 78/100); it was first detected on 2026-10-11. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.

Is uat.base.bh.edu.pk safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on uat.base.bh.edu.pk. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used uat.base.bh.edu.pk?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesMetaMask · PhishDestroy · SEAL 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 6 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 11, 2026
Registration (base domain)bh.edu.pk · Created Mar 23, 2014 — Expires Mar 23, 2032
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 11, 2026score 78/1002 brand signals
Submitted URLhttp://uat.base.bh.edu.pk/
Favicon Hash
Observed page title
BSS Timetable
Automated brand references
Base Google
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 46 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
34.65.68.235
Network ASN
AS396982
Organization
Google LLC
Observed location
Zürich, CH
Server header
Apache/2.4.52 (Ubuntu)

Nameservers 2

  • cruz.ns.cloudflare.com
  • nile.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-09 06:08:23
Valid until
2026-12-08 06:08:22
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint05632030b3c35c8fd3fa7fc52a7b171fc3ce4ed814ab020edc3f7443c769eee0
Certificate names · 3 SANs
  • api.base.bh.edu.pk
  • prototype.base.bh.edu.pk
  • staging.base.bh.edu.pk

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-22 10:38:16 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 10:38:16 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:38:16 UTC last content: 2026-10-22 10:38:16 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of uat.base.bh.edu.pk · checked Oct 12, 2026

57
Needs Work
Performance
FCP
7.15s
First Contentful Paint
LCP
11.07s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
7.15s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history10

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · Recorded state

    Unknown→live_content

    content_served

Earlier observations 5
  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  3. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  4. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  5. Availability monitor · First collection record

    Reachable

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    4/92 engine detections

    View source
  3. Added to PhishDestroy

    uat.base.bh.edu.pk

    View source
  4. URLScan

    Page captured

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

uat.base.bh.edu.pk

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Official reporting routes

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including uat.base.bh.edu.pk)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/uat.base.bh.edu.pk"
  title="PhishDestroy threat report for uat.base.bh.edu.pk"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>