Skip to security report
Analytics Dashboard
Domain security and threat intelligence
stealaneggitem.blogspot.com favicon

stealaneggitem.blogspot.com

In short

stealaneggitem.blogspot.com is a Roblox impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (76/100). Registrar: Google Blogger. Status: Last known active. Hosting: Google LLC. VirusTotal: 2/91 engines flag it. Do not enter credentials or connect a wallet.

“Speed Keyboard Escape · Free Items & Boosts”

Registrar
Google Blogger
Resolved IP
142.250.154.132
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 2/91 Automated brand label: Roblox
Sep 14, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 2. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
2 / 91
engine detections
Google Safe Browsing
No threat flag
Page captures
3
open gallery
Source evidenceVirusTotal 2 / 91 5 sources

VirusTotal

2 / 91 engine detections

Open report

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
2 / 91
Page captures
3
Page captures Source results Registration record

PhishDestroy threat report

Overview

stealaneggitem.blogspot.com is a Blogger-hosted impersonation phishing page that presents itself as "Speed Keyboard Escape · Free Items & Boosts". It targets players looking for free in-game items, and its subdomain name suggests a lure built around a game item. PhishDestroy first recorded it on 2026-09-14. As of 2026-10-19 the site was still online with its content live. The subdomain name refers to an egg item, while the page title advertises a different game, Speed Keyboard Escape.

How the scam works

Free-items and boost pages work by copying the look and language of a legitimate game or giveaway. The page tells visitors they can claim rare items or boosts at no cost if they first log in, "verify" their account, or complete a set of steps. Whatever the visitor enters, such as usernames, passwords, email addresses or one-time codes, goes to the operator, not to the game. The real loss is the account itself, along with any inventory, currency or linked payment methods it holds.

Evidence

Detection by security vendors is thin. On 2026-09-28, 2 of 91 VirusTotal engines flagged the page, Forcepoint ThreatSeeker and VIPRE. PhishDestroy is currently the only blocklist that lists it. With this little coverage, most browsers and security filters will probably still load the page without a warning, so readers cannot count on an automatic block.

Infrastructure

The operator has not registered a domain of its own. The page sits on a free Blogger subdomain, served from Google LLC infrastructure in the US. Its HTTPS certificate comes from Google Trust Services (WE2), which every blogspot.com site receives automatically. The padlock therefore only shows that the connection is encrypted and says nothing about whether the page is trustworthy.

What to do

Free items are not handed out through Blogger pages. If you entered a game login on this site, change that password at once, as well as the password of any other account where you reused it. Turn on two-factor authentication, sign out all active sessions, and check that the recovery email and phone number on the account have not been changed. If the game account has purchases or payment cards linked to it, review recent transactions and contact the game's support team. Defenders should block the subdomain and report it to Google's Blogger abuse channel, since the page was still serving its lure as of 2026-10-19.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-14T10:28:41Z

Observed: · Retrieved:

Uuid
01a09f76-1ce9-767c-85fe-875da60c1a8c
Final url
https://stealaneggitem.blogspot.com/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://stealaneggitem.blogspot.com/",
        "from": "https://stealaneggitem.blogspot.com/",
        "status": 302
    }
]
Ip
142.251.110.132
Ptr
bz-in-f132.1e100.net
Contacted domains
[
    "oyster.ignimgs.com",
    "analytics.tiktok.com",
    "i.imgur.com",
    "fonts.gstatic.com",
    "speedescape.pages.dev",
    "analytics-ipv6.tiktokw.us",
    "topgames.gg",
    "cdnjs.cloudflare.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "23.50.131.221",
    "151.101.193.135",
    "199.232.196.193",
    "142.251.13.94",
    "95.100.110.26",
    "188.114.96.3",
    "188.114.97.3",
    "104.17.24.14",
    "142.250.154.95",
    "142.251.110.132"
]
Asns
[
    "20940",
    "54113",
    "15169",
    "13335"
]
Countries
[
    "DE",
    "US"
]
Document hash
96031891e9629b532d541a6ebdcfe4fe39c5365e648926e636c2293500c7bba2
Globals
[
    "TiktokAnalyticsObject",
    "ttq",
    "openLocker",
    "closeModal",
    "startFakeGen",
    "TiktokJelly",
    "_jelly_sdks"
]
Cookies
[
    "_ttp",
    "_tt_enable_cookie",
    "ttcsid",
    "ttcsid_D5U8LMJC77UECCBSGL4G"
]
Storage keys
[
    "tt_sessionId",
    "tt_appInfo",
    "tt_pixel_session_index"
]
Tls
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE2",
    "subject": "misc-sni.blogspot.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-02T08:38:52Z",
    "valid_from": "2026-08-10T08:38:53Z"
}
Domain age days
15
Apex age days
15
Tls age days
35
Tls valid days
83
Requests
31
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "GSE",
    "content-type": "text/html; charset=UTF-8",
    "x-content-type-options": "nosniff"
}
Cloudflare Radar · 2026-09-21T07:59:10Z

Observed: · Retrieved:

Uuid
19134701-d783-4d18-8836-92276a7fc022
Final url
https://stealaneggitem.blogspot.com/
Status
200
History
[
    {
        "url": "https://stealaneggitem.blogspot.com/",
        "status": 200
    }
]
DOM structure hash
2a2ad974ac4842fd0b61224a48077ead9a371f0663d8af33bf0c5245773a7051
Document hash
96031891e9629b532d541a6ebdcfe4fe39c5365e648926e636c2293500c7bba2
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "stealaneggitem.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    },
    {
        "name": "stealaneggitem.blogspot.com",
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dnssec valid
false
Ip
172.217.23.225
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2000-07-31T21:38:58Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T21:38:58Z",
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ]
}
VirusTotal · 2026-10-12T18:01:44Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "malware",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
MarkMonitor Inc.
Created
2000-07-31T21:38:58Z
Expires
2027-07-31T21:38:58Z
Updated
2026-06-29T10:34:06Z
First seen
2026-09-14T04:17:34Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2607:f8b0:4001:c08::84"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "74.125.69.132"
    },
    {
        "ttl": 300,
        "type": "CNAME",
        "value": "blogspot.l.googleusercontent.com"
    }
]
Dns at
2026-10-12T18:02:18Z
Jarm
27d40d40d29d40d1dc42d43d00041ded961c16c68658e95145597cf992c36c
Certificate
{
    "san": [
        "misc-sni.blogspot.com",
        "blogspot.ae",
        "*.blogspot.ae",
        "blogspot.al",
        "*.blogspot.al",
        "blogspot.am",
        "*.blogspot.am",
        "blogspot.ba",
        "*.blogspot.ba",
        "blogspot.be"
    ],
    "issuer": "Google Trust Services / WR2",
    "serial": "314459051a6865d30a64aaa66545849a",
    "sha256": "4857922e4732af9da27dfbbe57b2c741da8a8af83def47e9345092cbed8e2508",
    "subject": "misc-sni.blogspot.com",
    "valid_to": "2026-12-11T20:01:21Z",
    "valid_from": "2026-09-18T20:01:22Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2000-07-31T07:00:00Z",
    "updated": "2026-06-29T10:34:06Z",
    "expires": "2027-07-31T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited",
        "serverDeleteProhibited",
        "serverTransferProhibited",
        "serverUpdateProhibited"
    ],
    "nameservers": [
        "ns1.google.com",
        "ns2.google.com",
        "ns3.google.com",
        "ns4.google.com"
    ],
    "dnssec": "unsigned"
}

Questions about stealaneggitem.blogspot.com

Is stealaneggitem.blogspot.com legit?

No. PhishDestroy classifies stealaneggitem.blogspot.com as a Roblox impersonation page (risk: critical, 76/100); it was first detected on 2026-09-14. VirusTotal: 2/91 engines flag it. Treat the site as unsafe.

Is stealaneggitem.blogspot.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on stealaneggitem.blogspot.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 stealaneggitem.blogspot.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 matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 3 captures

Primary capture 1 / 3
SourcePrimary capture
Recorded2026-09-14 10:25 UTC
StateStored capture
Position1 / 3
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Reputation abuse score 0/100 20 reports Port ScanHackingBrute-ForceSSH checked Oct 21, 2026
Platform provider Google Blogger US(US)
Abuse contact["abusecomplaints@markmonitor.com", "72d89d094faaef2es@"]
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedSep 14, 2026
DOM Analysisanalyzed Sep 21, 2026score 76/1001 brand signal
Favicon Hash
Observed page title
Speed Keyboard Escape · Free Items & Boosts
Automated brand references
Roblox
TLS Certificate
Issued by Google Trust Services / WE2 · stored validity ends in 35 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
142.250.154.132
Network ASN
AS15169
Organization
Google LLC
Observed location
Mountain View, US
Server header
GSE

Nameservers 4

  • ns1.google.com
  • ns2.google.com
  • ns3.google.com
  • ns4.google.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE2
Valid from
2026-09-04 08:05:57
Valid until
2026-11-27 08:05:56
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-20 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbae5c6fbbbc165668f5bb3bd72ca83c821e993d218ebbef8483371d5863e2614
Certificate names · 70 SANs
  • blogspot.ae
  • blogspot.al
  • blogspot.am
  • blogspot.ba
  • blogspot.be
  • blogspot.bg
  • blogspot.ca
  • blogspot.ch
  • blogspot.cl
  • blogspot.co.at
  • blogspot.co.id
  • blogspot.co.il
  • blogspot.co.ke
  • blogspot.co.nz
  • blogspot.co.uk
  • blogspot.co.za
  • blogspot.com
  • blogspot.com.ar
  • blogspot.com.au
  • blogspot.com.br
  • blogspot.com.by
  • blogspot.com.co
  • blogspot.com.cy
  • blogspot.com.ee
  • blogspot.com.eg
  • blogspot.com.es
  • blogspot.com.mt
  • blogspot.com.ng
  • blogspot.com.tr
  • blogspot.com.uy
  • blogspot.cz
  • blogspot.de
  • blogspot.dk
  • blogspot.fi
  • blogspot.fr
  • blogspot.gr
  • blogspot.hk
  • blogspot.hr
  • blogspot.hu
  • blogspot.ie
  • blogspot.in
  • blogspot.is
  • blogspot.it
  • blogspot.jp
  • blogspot.kr
  • blogspot.li
  • blogspot.lt
  • blogspot.lu
  • blogspot.md
  • blogspot.mk
  • blogspot.mx
  • blogspot.my
  • blogspot.nl
  • blogspot.no
  • blogspot.pe
  • blogspot.pt
  • blogspot.qa
  • blogspot.ro
  • blogspot.rs
  • blogspot.ru
  • blogspot.se
  • blogspot.sg
  • blogspot.si
  • blogspot.sk
  • blogspot.sn
  • blogspot.tw
  • blogspot.ug
  • blogspot.vn
  • bp.blogspot.com
  • misc-sni.blogspot.com

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

viewdns.info · 142.250.154.132rapiddns.io

Latest Classified Outcome 2026-10-22 10:06: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:06:54 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 10:06:54 UTC last content: 2026-10-22 10:06: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.
Technologies · 5 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 91 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 2 detections
Forcepoint ThreatSeeker
VIPRE
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of stealaneggitem.blogspot.com · checked Sep 21, 2026

62
Needs Work
Performance
FCP
2.9s
First Contentful Paint
LCP
34.68s
Largest Contentful Paint
CLS
0.144
Cumulative Layout Shift
TBT
119ms
Total Blocking Time
SI
3.53s
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 history18

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

  6. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  7. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  8. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  9. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  10. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  11. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  12. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  13. Availability monitor · First collection record

    Reachable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    2/91 engine detections

    View source
  3. Added to PhishDestroy

    stealaneggitem.blogspot.com

    View source

Check for cloaking

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

stealaneggitem.blogspot.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery SSL Labs Certificate hostname mismatch CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 stealaneggitem.blogspot.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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

Request a correction or appeal How PhishDestroy works
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/stealaneggitem.blogspot.com"
  title="PhishDestroy threat report for stealaneggitem.blogspot.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>