Skip to security report
hadiah-shopee129.blogspot.com favicon
Domain security and threat intelligence

hadiah-shopee129.blogspot.com

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

On 2026-10-20, http://hadiah-shopee129.blogspot.com/ redirected to https://hadiah-shopee129.blogspot.com/. The destination page displays a Shopee-branded layout featuring promotional banners for a prize giveaway, product images including electronics and clothing, and text inviting visitors to claim winnings using a specific winner code. Additional sections show contact details and corporate imagery.

Page title: “Blog not found”

More about the sources
Recorded security signals

Stored VirusTotal result: 19/92 engines flagged. Analysis time (as stored): 2026-10-22 16:33 UTC. Retrieved (as stored): 2026-11-16 21:01 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 19/92
Resolved IP
United States74.125.205.132Google LLC
First seen by PhishDestroy
2026-10-20
Page captures
open gallery
2026-10-20

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded hadiah-shopee129.blogspot.com on 2026-10-20. Stored VirusTotal result: 19/92 engines flagged. Analysis time (as stored): 2026-10-22 16:33 UTC. Retrieved (as stored): 2026-11-16 21:01 UTC. Risk: critical (evidence score 95/100). Status: HTTP 404 · Content unavailable. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
VirusTotal
19 / 92
Hosting
United States74.125.205.132Google LLC
Page captures
2

URLScan capture · 2026-10-20 06:24 UTC · SHA-256 5c61569a…d83d960

PhishDestroy analysis, reviewed version

On 2026-10-20, http://hadiah-shopee129.blogspot.com/ redirected to https://hadiah-shopee129.blogspot.com/. The destination page displays a Shopee-branded layout featuring promotional banners for a prize giveaway, product images including electronics and clothing, and text inviting visitors to claim winnings using a specific winner code. Additional sections show contact details and corporate imagery.

The stored VirusTotal domain result reports 19 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "phishing".

Source evidenceVirusTotal 19 / 92 4 sources

VirusTotal

19 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 15 fields
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

Source
VirusTotal
Result state
observed
Numerator
19
Denominator
92
Vendors
alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, LevelBlue, Lionic, MalwareURL, Netcraft, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Observed at
2026-10-22 16:33:28
Checked at
2026-11-16 22:01:41
Fetched at
2026-11-16 21:01:42

URLScan

Malicious

SHA-256 d65b2aca…719d326

Open report
URLScanOriginal source recordObserved: 22 fields
Separate monitor record · 2026-11-17 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a157fb-a189-778a-a825-f9c29e52da12
Score
100
Malicious
✓
Result at
2026-11-17T04:30:44Z
Enriched at
2026-11-17T09:16:14Z
Source timestamps
Urlscan result at: 2026-11-17 05:30:44; Urlscan enriched at: 2026-11-17 10:16:14
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
hadiah-shopee129.blogspot.com: Shopee-branded lucky draw
AI description
PhishDestroy records a redirect on 2026-10-20 to hadiah-shopee129.blogspot.com featuring a Shopee-branded promotional prize claim page.
AI summary
On 2026-10-20, http://hadiah-shopee129.blogspot.com/ redirected to https://hadiah-shopee129.blogspot.com/. The destination page displays a Shopee-branded layout featuring promotional banners for a prize giveaway, product images including electronics and clothing, and text inviting visitors to claim winnings using a specific winner code. Additional sections show contact details and corporate imagery. The stored VirusTotal domain result reports 19 detections out of 92 engines. ESET reported "phishing"; VIPRE reported "phishing".
AI generated by
threat-v6-gemini
AI generated at
2026-11-16T22:13:02Z
Revision
b4065af1db58f4ce1341e9c1e71c8b1b1e9933523d99865146a1c78a3a529ff6
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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

Collected source details

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

Every stored field, with its source and date
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Phishing Phishing Security threats

Questions about hadiah-shopee129.blogspot.com

Is hadiah-shopee129.blogspot.com legit?

PhishDestroy rates hadiah-shopee129.blogspot.com as critical risk (evidence score 95/100) from the recorded evidence; it was first recorded on 2026-10-20. Stored VirusTotal result: 19/92 engines flagged. Analysis time (as stored): 2026-10-22 16:33 UTC. Retrieved (as stored): 2026-11-16 21:01 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is hadiah-shopee129.blogspot.com safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on hadiah-shopee129.blogspot.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used hadiah-shopee129.blogspot.com?

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Downloaded a file — do not open it and scan the device with security software

Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (2)

All capture links and hashes (2)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Shopee report ↗
IP Reputation United States74.125.205.132 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has a low abuse score, but the domain itself is recognized as phishing. 0 reports checked 2026-11-17 last reported · outside the counted period
Platform provider blogspot.com
HTTP Status404 Not Found
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-10-20
Submitted URLhttp://hadiah-shopee129.blogspot.com/
Observed page title
Blog not found
TLS Certificate
Issued by WE2

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States74.125.205.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
United StatesMountain 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
WE2
Hostname match
Not checked
Collection source
PhishDestroy collector

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-11-22 11:15 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Resolved
Latest HTTP observation Inactive Http No Content 70% 2026-11-22 11:15 UTC
RDAP registration
Observed timeline current episode first observed: 2026-11-17 02:22 UTC first terminal observation: 2026-11-17 02:22 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
Open complete records

VirusTotal Analysis

19 / 92 security vendors flagged this domain
View on VT
Last analyzed
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Emsisoft
Fortinet
Netcraft
SOCRadar
URLQuery
Kaspersky
LevelBlue
Gridinsoft
MalwareURL
BitDefender
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

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://hadiah-shopee129.blogspot.com/
Final URL: https://hadiah-shopee129.blogspot.com/
shopee
Response
HTTP 200
HTML body
908.7 KB
Compressed
632.6 KB
Links
1 internal · 22 external
Detected technologies
vuebootstrap
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0
Content-Encoding: gzip
Server: GSE
Security headers present
X-Content-Type-OptionsX-XSS-Protection
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: a1495da3cf3db37bf105a12658636ff628fee7b73975b9200049af7747e60b1f
Open Graph title: shopee
Saved response-header values · 12
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Cache-Control
private, max-age=0
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Tue, 20 Oct 2026 13:11:08 GMT
Etag
W/"c58bf51fb11949e4d976e017739b847bcc59f2666f5f1fce1f9c10babd0e0a1e"
Expires
Tue, 20 Oct 2026 13:11:08 GMT
Last-Modified
Wed, 06 Nov 2024 03:03:16 GMT
Server
GSE
Transfer-Encoding
chunked
X-Content-Type-Options
nosniff
X-XSS-Protection
1; mode=block

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

Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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

All stored data92
Open complete records

Captured network requests

Network requests: 51 SHA-256 hashes: 51 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-16 21:04 UTC.

Open this scan on URLScan 01a157fb-a189-778a-a825-f9c29e52da12 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
Blog not found
Crawler
Blog nicht gefunden.
hadiah-shopee129.blogspot.com
Stored observation history7

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

    No page content

    no page content in the HTTP response

  2. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  3. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  4. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  5. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

Earlier observations 2
  1. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

  2. Availability monitor · Recorded state

    No page content

    no page content in the HTTP response

All retained availability observations17
Open complete records

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    hadiah-shopee129.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · Cloudflare Radar: Malicious · Automated brand label: ShopeePay · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+9576 d 15 h
  3. VirusTotal analysis with detections+51 h 25 min
  1. VirusTotal

    19/92 engine detections

    +51 h 22 min
  2. Wayback Machine

    Page archived

    +3 min
  3. Added to PhishDestroy

    hadiah-shopee129.blogspot.com

    +6 h 43 min
  4. URLScan

    Malicious

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

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 hadiah-shopee129.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

Stay Informed, Stay Safe

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

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 →
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/hadiah-shopee129.blogspot.com"
  title="PhishDestroy threat report for hadiah-shopee129.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>