Skip to security report
Domain security and threat intelligence
webmail-oauth.lygrunfeng.com favicon

webmail-oauth.lygrunfeng.com

In short

webmail-oauth.lygrunfeng.com is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (90/100). Registrar: Gname. Status: Last known active. Hosting: HostPapa. VirusTotal: 12/92 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

“SharePoint Online”

Registrar
Gname
Resolved IP
192.255.130.215
Registered
Feb 27, 2008
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation
VirusTotal detections: 12/92 Spamhaus DBL: DBL_ABUSED_PHISH Stored blocklist matches: 1
Oct 22, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 12. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
engine detections
Google Safe Browsing
Page captures
open gallery
Domain age
Source evidenceVirusTotal 12 / 92 6 sources

VirusTotal

12 / 92 engine detections

Open report

Spamhaus DBL

DBL_ABUSED_PHISH

OTX

no 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
12 / 92
Page captures
9

PhishDestroy threat report

Overview

PhishDestroy listed webmail-oauth.lygrunfeng.com as a suspicious domain after its intake on 2026-10-22. The recorded page returned HTTP 200 and carries the title “SharePoint Online”. The domain was first seen by PhishDestroy on 2026-10-22.

How the scam works

The malicious detections suggest the site is being used for phishing, a common tactic where attackers host pages that imitate legitimate services to capture login credentials. No specific credential‑harvesting form was observed on the captured page, so the exact method remains uncertain.

Evidence

VirusTotal reported 12 malicious detections from 92 engines on 2026-10-22, including BitDefender, Fortinet, G‑Data and others. urlscan.io classified the URL as malicious with a phishing category and a score of 100 on the same date. Google Safe Browsing did not flag the domain, OTX showed no pulses, and external blocklists returned zero hits while PhishDestroy’s internal list marked it true.

Infrastructure

The domain’s A record points to 192.255.130.215, hosted by HostPapa in the United States, and is served through Cloudflare’s DNS. The TLS certificate is a Let’s Encrypt certificate issued on 2026-09-08 and valid until 2026-12-07. The domain was registered 43 days ago, and the apex domain lygrunfeng.com is 1,345 days old.

What to do

Visitors should not enter any credentials on the site; if they have, they should change passwords and enable multi‑factor authentication on the affected accounts. Administrators should block the exact hostname and monitor network logs for connections to the recorded IP address. Adding the domain to internal blocklists and updating web filtering rules can help prevent future access.

Collected source details

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

URLScan · 2026-10-22T08:46:09Z

Observed: · Retrieved:

Uuid
01a162c9-e9cf-7748-9798-f50165258894
Final url
https://webmail-oauth.lygrunfeng.com/yuin/auth38412241/cpseszssbvjovaq
Status
200
Ip
192.255.130.215
Ptr
mail.yxtsz.com
Contacted domains
[
    "code.jquery.com",
    "ajax.googleapis.com",
    "bafkreibo2imbts2at4vudcnu2frf4qxp62qjxm2zsesegokwe25jlebpde.ipfs.dweb.link"
]
Contacted IP addresses
[
    "151.101.1.155",
    "173.194.114.95",
    "192.255.130.215"
]
Asns
[
    "54113",
    "15169",
    "36352"
]
Countries
[
    "US"
]
Document hash
ab421eadd02bd2cb42eb50f3c2e3cec5cd569749718bfd16cb52f2fec61767b5
Globals
[
    "$",
    "jQuery",
    "_0x3452",
    "_0xce4d28",
    "_0x3c6c",
    "_0x3aad84",
    "_0x202291",
    "_0x16aa13",
    "_0x50058f",
    "_0x5f1a61"
]
Tls
{
    "san": [
        "webmail-oauth.lygrunfeng.com"
    ],
    "cipher": "AES_256_GCM",
    "issuer": "YR2",
    "subject": "webmail-oauth.lygrunfeng.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-07T23:30:24Z",
    "valid_from": "2026-09-08T23:30:25Z"
}
Domain age days
43
Apex age days
1345
Tls age days
43
Tls valid days
89
Requests
6
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 87,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "genericemail"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Generic Email"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000"
}
Cloudflare Radar · 2026-10-22T13:20:48Z

Observed: · Retrieved:

Uuid
c2fcad19-bb8f-4414-a191-340f798b23d5
Final url
https://webmail-oauth.lygrunfeng.com/
Status
200
History
[
    {
        "url": "https://webmail-oauth.lygrunfeng.com/",
        "status": 200
    }
]
DOM structure hash
c8e20ef3eb346edf53a8fadffe0b41a7b544b6a077877cdeecb209b2e3b19739
Document hash
ab421eadd02bd2cb42eb50f3c2e3cec5cd569749718bfd16cb52f2fec61767b5
Phishing v2
[
    "phishing"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "webmail-oauth.lygrunfeng.com",
        "type": "A",
        "value": "192.255.130.215"
    }
]
Dnssec valid
false
Ip
192.255.130.215
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2008-02-27T00:13:03Z",
    "updated": "2026-08-06T09:54:59Z",
    "expires": "2027-02-27T00:13:03Z",
    "nameservers": [
        "arturo.ns.cloudflare.com",
        "margot.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-22T09:56:35Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 47,
    "malicious": 12,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Gname.com Pte. Ltd.
Created
2008-02-27T00:13:03Z
Expires
2027-02-27T00:13:03Z
Updated
2026-10-15T09:55:01Z
First seen
2026-09-09T01:09:47Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "192.255.130.215"
    }
]
Dns at
2026-10-22T09:56:49Z
Jarm
3fd3fd0003fd3fd00042d42d0000002059a3b916699461c5923779b77cf06b
Certificate
{
    "san": [
        "webmail-oauth.lygrunfeng.com"
    ],
    "issuer": "Let's Encrypt / YR2",
    "serial": "69a5d2efbfcefa8054f26909ba86e3609b7",
    "sha256": "c916b6890a7eb422fbfaedf1b94a5130f46f58420c5ae1262d94cb958189ec22",
    "subject": "webmail-oauth.lygrunfeng.com",
    "valid_to": "2026-12-07T23:30:24Z",
    "valid_from": "2026-09-08T23:30:25Z"
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "registrar_iana_id": "1923",
    "registrar_url": "http://www.gname.com",
    "created": "2008-02-27T00:13:03Z",
    "updated": "2026-08-06T09:54:59Z",
    "expires": "2027-02-27T00:13:03Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "arturo.ns.cloudflare.com",
        "margot.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Website checks · 2026-10-22T13:26:35Z
Caa records
{
    "domain": "webmail-oauth.lygrunfeng.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-22T13:13:25Z",
    "first": "2026-10-22T13:13:25Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 14099
}
Page title and metadata
{
    "title": "SharePoint Online"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google APIs",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "jQuery",
            "company": "JS Foundation",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://bafkreibo2imbts2at4vudcnu2frf4qxp62qjxm2zsesegokwe25jlebpde.ipfs.w3s.link/",
        "https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js",
        "https://code.jquery.com/jquery-3.1.1.min.js"
    ],
    "third_party_scripts": 4
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 152,
        "wait": 303,
        "connect": 149,
        "download": 0
    },
    "response_ms": 606
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        21,
        22,
        25,
        80,
        110,
        143,
        443,
        587,
        993,
        995
    ]
}
Carbon
{
    "bytes": 31218,
    "co2_grams": 0.0011,
    "cleaner_than": 47
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.44.216",
            "host": "arturo.ns.cloudflare.com"
        },
        {
            "ip": "172.64.34.167",
            "host": "margot.ns.cloudflare.com"
        }
    ],
    "zone": "lygrunfeng.com"
}
Location
{
    "ip": "192.255.130.215",
    "asn": "36352",
    "org": "HostPapa",
    "city": "Dallas",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YR2",
    "subject": "webmail-oauth.lygrunfeng.com"
}
DNS records
{
    "A": [
        "192.255.130.215"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000",
    "message": "HSTS header does not include all subdomains."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "192.255.130.215",
    "family": 4
}
Redirects
{
    "chain": [
        "https://webmail-oauth.lygrunfeng.com"
    ]
}
Subdomains
{
    "count": 3,
    "subdomains": [
        "webmail-authb.lygrunfeng.com",
        "webmail-authblk.lygrunfeng.com",
        "webmail-autho.lygrunfeng.com"
    ]
}
Tech stack
{
    "technologies": [
        "Nginx",
        "jQuery",
        "HSTS",
        "HTTP/3"
    ]
}
Registration record
{
    "registrar": "Gname.com Pte. Ltd.",
    "created": "2008-02-27T00:13:03Z",
    "updated": "2026-08-06T09:54:59Z",
    "expires": "2027-02-27T00:13:03Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "arturo.ns.cloudflare.com",
        "margot.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    }
}

Questions about webmail-oauth.lygrunfeng.com

Is webmail-oauth.lygrunfeng.com legit?

No. PhishDestroy classifies webmail-oauth.lygrunfeng.com as a phishing page (risk: critical, 90/100); it was first detected on 2026-10-22. VirusTotal: 12/92 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is webmail-oauth.lygrunfeng.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on webmail-oauth.lygrunfeng.com. 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 webmail-oauth.lygrunfeng.com?

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 matchesOpenPhish · PhishDestroy 2
OpenPhish Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 9 captures

Domain details

Domain
IP Reputation abuse score 0/100 0 reports checked Oct 22, 2026
Registrar (base domain) Gname SG(SG)
Registration (base domain)lygrunfeng.com · Created Feb 27, 2008 — Expires Feb 27, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 83/100
Submitted URLhttp://webmail-oauth.lygrunfeng.com/yuin/auth22053149/cpsesvlmvqlqakz
Favicon Hash
Observed page title
SharePoint Online
TLS Certificate
Issued by Let's Encrypt / YR2 · stored validity ends in 46 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
192.255.130.215
Network ASN
AS36352
Organization
HostPapa
Observed location
Dallas, US
Server header
nginx

Nameservers 2

  • arturo.ns.cloudflare.com
  • margot.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR2
Valid from
2026-09-08 23:30:25
Valid until
2026-12-07 23:30:24
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc916b6890a7eb422fbfaedf1b94a5130f46f58420c5ae1262d94cb958189ec22
Certificate names · 1 SAN
  • webmail-oauth.lygrunfeng.com

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

Technologies · 6 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

12 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 12 detections
BitDefender
CRDF
CyRadar
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
SOCRadar
VIPRE
Webroot
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://webmail-oauth.lygrunfeng.com/yuin/auth22053149/cpsesvlmvqlqakz
Final URL: https://webmail-oauth.lygrunfeng.com/yuin/auth22053149/cpsesvlmvqlqakz
SharePoint Online
Response
HTTP 200
HTML body
30.5 KB
Compressed
12.9 KB
Links
0 internal · 0 external
Detected technologies
jquerynginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 22 Oct 2026 13:13:47 GMT
Etag
W/"6aa0a90c-79f2"
Last-Modified
Wed, 09 Sep 2026 00:32:12 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    12/92 engine detections

    View source
  3. Added to PhishDestroy

    webmail-oauth.lygrunfeng.com

    View source

Check for cloaking

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

webmail-oauth.lygrunfeng.com

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 webmail-oauth.lygrunfeng.com)
  • 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/webmail-oauth.lygrunfeng.com"
  title="PhishDestroy threat report for webmail-oauth.lygrunfeng.com"
  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>