Skip to security report
Domain security and threat intelligence
drivespa.ru favicon

drivespa.ru

In short

drivespa.ru is a Telegram impersonation page detected by PhishDestroy on 2026-10-10. Risk: critical (100/100). Status: Last known active. Hosting: Beget LLC. VirusTotal: 15/92 engines flag it. Do not enter credentials or connect a wallet.

“drivespa.ru”

Resolved IP
5.101.153.83
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
VirusTotal detections: 15/92 Automated brand label: Telegram
OTX: 33 refs Oct 11, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 15. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
OTX
community references
Page captures
open gallery
Source evidenceVirusTotal 15 / 92 · OTX 33 references 5 sources

VirusTotal

15 / 92 engine detections

Open report

OTX

33 community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
15 / 92
OTX
33 community refs
Page captures
6

PhishDestroy threat report

Overview

drivespa.ru is classified by PhishDestroy as an impersonation phishing page, a site built to pass itself off as a service people already trust. PhishDestroy first flagged it on 2026-10-11. As of 2026-10-19 it was still online and serving live content, so anyone reaching it today can still be exposed. Its page title is simply the domain name and does not reveal which brand it copies.

How the scam works

Impersonation pages copy the look of a familiar brand, including its logo, layout and wording, so visitors believe they are on the real site. The visitor is then asked to sign in, verify an account, confirm a payment or submit personal details. Whatever is typed goes straight to the operators. Stolen credentials are used to take over accounts, card data is used for fraud, and personal details feed follow-up scams. A plain, generic title like this one gives no clue to the deception, so the visual copy of the brand does all the work.

Evidence

Fifteen of 92 VirusTotal engines flagged the domain as of 2026-10-12. That is a minority, but the flagging vendors are independent of one another and include BitDefender, Fortinet, Forcepoint ThreatSeeker, G-Data, Gridinsoft, alphaMountain.ai, CyRadar and Chong Lua Dao. The domain also appears in 33 AlienVault OTX threat pulses, which means many researchers have tied it to malicious activity. PhishDestroy lists it on its own blocklist.

Infrastructure

The site resolves to 5.101.153.83 on the Beget LLC network in Russia. Beget is a mainstream Russian shared-hosting provider, and phishing operators often use low-cost commodity hosting like it to stand up pages quickly. A .ru domain on domestic hosting suggests the operation may be aimed mainly at Russian-speaking users.

What to do

Do not enter anything on drivespa.ru. If you typed a password there, change it right away on the genuine service and on any other account that shares it, then turn on two-factor authentication. If you entered card or banking details, call your bank to block the card and dispute any charges. Watch for follow-up emails, SMS or calls that refer to your submission, because these are a common second stage. Defenders should block the domain and the IP 5.101.153.83 at the DNS, proxy and email-gateway level, and should search logs for any users who visited it.

Collected source details

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

URLScan · 2026-10-01T09:30:27Z

Observed: · Retrieved:

Uuid
01a0f6cc-a5e0-76ea-9896-0c8e8f8e92ef
Final url
http://drivespa.ru/
Status
200
Redirects
[
    {
        "to": "https://drivespa.ru/",
        "from": "http://drivespa.ru/",
        "status": 307
    },
    {
        "to": "http://drivespa.ru/",
        "from": "https://drivespa.ru/",
        "status": 307
    }
]
Ip
5.101.153.83
Ptr
m2.bober.beget.com
Contacted domains
[
    "cp.beget.com",
    "fonts.gstatic.com",
    "use.fontawesome.com",
    "cdnjs.cloudflare.com",
    "fonts.googleapis.com",
    "code.jquery.com"
]
Contacted IP addresses
[
    "142.251.110.94",
    "178.248.232.144",
    "2606:4700:3033::ac43:8ef5",
    "2a00:1450:400a:1001::5f",
    "2a04:4e42:400::411",
    "104.17.25.14",
    "5.101.153.83"
]
Asns
[
    "15169",
    "51115",
    "13335",
    "54113",
    "198610"
]
Countries
[
    "US",
    "RU",
    "CH"
]
Linked domains
[
    "beget.com",
    "cp.beget.com",
    "join.skype.com"
]
Document hash
558b25e93f64fdd42eed0dac7cb7509e3d65668d4ee9fdf3ab40ff4729f6349c
Globals
[
    "_",
    "$",
    "jQuery",
    "browser",
    "instructions",
    "clearCache",
    "toggleInstruction",
    "language",
    "ru",
    "en",
    "mainDiv",
    "data"
]
Domain age days
3892
Apex age days
3892
Requests
19
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx-reuseport/1.21.1",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-12T11:21:31Z

Observed: · Retrieved:

Uuid
399073c7-506b-4bdc-a1ce-1f3bc5ea7831
Final url
https://drivespa.ru/
History
[
    {
        "url": "https://drivespa.ru/",
        "status": 0
    }
]
DOM structure hash
433a5e367a2aeb4769756ee4cc70d4ffb3e81ed2c2fddf9de5834d9d14dd2a4d
Domain risks
[
    "Parked & For Sale Domains",
    "Security Risks"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "drivespa.ru",
        "type": "A",
        "value": "5.101.153.83"
    }
]
Dnssec valid
false
Registration record
{
    "registrar": "REGRU-RU",
    "created": "2018-03-07T14:18:46Z",
    "expires": "2027-03-07T14:18:46Z",
    "nameservers": [
        "ns1.beget.com",
        "ns2.beget.com"
    ]
}
VirusTotal · 2026-10-11T23:57:39Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 45,
    "malicious": 15,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "malicious",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "malware",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "malicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Popularity
{
    "Cisco Umbrella": 889222
}
Registrar
REGRU-RU
First seen
2023-10-05T12:48:46Z
DNS records
[
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.com"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.pro"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.com"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns1.beget.ru"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.ru"
    },
    {
        "ttl": 300,
        "type": "NS",
        "value": "ns2.beget.pro"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "5.101.153.83"
    },
    {
        "ttl": 300,
        "type": "SOA",
        "rname": "hostmaster.beget.com",
        "value": "ns1.beget.com"
    }
]
Dns at
2026-10-11T23:57:52Z
Jarm
2ad2ad16d2ad2ad0002ad2ad2ad2ade58cf93292ac388f015f112b48278862
Certificate
{
    "issuer": "NO",
    "serial": "2794d3500b2507032ef680820a9287ddf9ec82f",
    "sha256": "05573c3897ab2516e43142797e73bc5d58c6ef6a883d43da761d05d7c66bdda5",
    "valid_to": "2022-07-17T11:11:39Z",
    "valid_from": "2019-07-18T11:11:39Z"
}
Registration record
{
    "registrar": "REGRU-RU"
}

Questions about drivespa.ru

Is drivespa.ru legit?

No. PhishDestroy classifies drivespa.ru as a Telegram impersonation page (risk: critical, 100/100); it was first detected on 2026-10-10. VirusTotal: 15/92 engines flag it. Treat the site as unsafe.

Is drivespa.ru safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on drivespa.ru. 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 drivespa.ru?

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 matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 6 captures

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 0 reports checked Oct 12, 2026
OTX tags 2026-10activeall-domainsblocklistcontentcryptocyber securitydomainsdrainerfraudiocmaliciousmonthlynextray+3 more
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 11, 2026
DOM Analysisanalyzed Oct 13, 2026score 98/1001 brand signal
Submitted URLhttp://drivespa.ru/
Favicon Hash
Observed page title
drivespa.ru
Automated brand references
Telegram
TLS Certificate
Issued by NO

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
5.101.153.83
Network ASN
AS198610
Organization
Beget Ltd
Observed location
St Petersburg, RU
Server header
nginx-reuseport/1.21.1

Location describes the IP network.

TLS certificate

Issuer
NO
Valid from
2019-07-18 11:11:39
Valid until
2022-07-17 11:11:39
Validity
Stored certificate expired
Collection time
2026-10-22 16:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint05573c3897ab2516e43142797e73bc5d58c6ef6a883d43da761d05d7c66bdda5

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:16:54 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:16:54 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:16:54 UTC last content: 2026-10-22 10:16:54 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

15 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
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.

Check for cloaking

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

Page titles differ

alive_content: raw=ok; http=200; via=http_proxy; server=nginx-reuseport/1.21.1

Browser
drivespa.ru
Crawler
Домен не прилинкован ни к одной из директорий на сервере!
drivespa.ru
Stored observation history9

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 4
  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

Recorded activity

4 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. AlienVault OTX

    33 community references

    View source
  3. VirusTotal

    15/92 engine detections

    View source
  4. Added to PhishDestroy

    drivespa.ru

    View source

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 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 drivespa.ru)
  • 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/drivespa.ru"
  title="PhishDestroy threat report for drivespa.ru"
  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>