Skip to security report
Dangerous

Phishing copy of Minecraft

minecrfatco.blogspot.com favicon
Domain security and threat intelligence

minecrfatco.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-11-09, minecrfatco.blogspot.com displayed a dark-themed page with a pixel-style MINECRAFT logo above a centered panel. The panel instructs visitors to enter their Username or ID and select a platform, with a text field labeled Username/ID and four icon buttons for Apple, Android, a game controller, and Windows, followed by a CONTINUE button. The page presents only this single entry form against a plain dark background, with no other visible sections or links.

Page title: “Minecraft Coins Generator”

More about the sources
Recorded security signals

Use caution — do not enter credentials or personal information.

Stored PhishDestroy threat listing Google Safe Browsing: threat flag recorded
Resolved IP
Germany192.178.183.132Google LLC
First seen by PhishDestroy
2026-11-09
Page captures
open gallery
2026-11-09

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 minecrfatco.blogspot.com on 2026-11-09. Google Safe Browsing flags it. Risk: critical (evidence score 80/100). Status: HTTP 404 · Content unavailable. Hosting: Google LLC. Do not enter credentials or connect a wallet.

Critical
Status
HTTP 404 · Content unavailable
Hosting
Germany192.178.183.132Google LLC
Page captures
6

Cloudflare Radar capture · 2026-11-09 13:43 UTC · SHA-256 2d8f7a44…f52e5e8

PhishDestroy analysis, reviewed version

On 2026-11-09, minecrfatco.blogspot.com displayed a dark-themed page with a pixel-style MINECRAFT logo above a centered panel. The panel instructs visitors to enter their Username or ID and select a platform, with a text field labeled Username/ID and four icon buttons for Apple, Android, a game controller, and Windows, followed by a CONTINUE button. The page presents only this single entry form against a plain dark background, with no other visible sections or links.

The stored VirusTotal domain result reports 0 detections out of 92 engines.

Source evidenceGoogle Safe Browsing: flagged 5 sources

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Page capture

SHA-256 6069a3de…51fc64f

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

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

UUID
01a1c06c-3469-70bc-b32f-368407a2524a
Score
0
Malicious
✗
Result at
2026-11-10T04:30:13Z
Enriched at
2026-11-10T09:12:23Z
Source timestamps
Urlscan result at: 2026-11-10 05:30:13; Urlscan enriched at: 2026-11-10 10:12:23

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 0 classifications

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 10 / 100 · 2026-11-09 13:47 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
10
Analyzed at
2026-11-09T13:47:16Z
Source timestamp
2026-11-09 14:47:16
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
minecrfatco.blogspot.com: Minecraft Username and Platform Entry Form
AI description
PhishDestroy records the minecrfatco.blogspot.com page showing a Minecraft-branded form asking for a username or ID and a platform choice before continuing.
AI summary
On 2026-11-09, minecrfatco.blogspot.com displayed a dark-themed page with a pixel-style MINECRAFT logo above a centered panel. The panel instructs visitors to enter their Username or ID and select a platform, with a text field labeled Username/ID and four icon buttons for Apple, Android, a game controller, and Windows, followed by a CONTINUE button. The page presents only this single entry form against a plain dark background, with no other visible sections or links. The stored VirusTotal domain result reports 0 detections out of 92 engines.
AI generated by
threat-v6-mimo
AI generated at
2026-11-09T13:46:10Z
Revision
e5a7dcc21393b368fe338f0efab32a026fe24f6f6ddb38bc5d60641282286cbd
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
VirusTotalOriginal source recordObserved: 13 fields
Open complete records
Website checksOriginal source recordRetrieved: 20 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
blogspot.com
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
11553

Trackers

Requests
16
Observed services
  • Name
    Amazon CloudFront
    Company
    Amazon
    Country
    US
    Category
    Hosting
    Requests
    11
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Analytics
    Company
    Google
    Country
    US
    Category
    Site Analytics
    Requests
    1
  • Name
    Sentry
    Company
    Sentry
    Country
    US
    Category
    Utilities
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://d9qn9uafc7mxn.cloudfront.net/89adedd.js
  • https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js
Third-party scripts
3

HTTP response

Reachable
Yes
HTTP status
302
Request timings, ms
DNS
6
TLS
26
Waiting
401
Connection
9
Download
0
Response time, ms
442

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

DNS servers

Nameservers
  • IP address
    216.239.34.10
    Host
    ns2.google.com
  • IP address
    216.239.32.10
    Host
    ns1.google.com
  • IP address
    216.239.36.10
    Host
    ns3.google.com
  • IP address
    216.239.38.10
    Host
    ns4.google.com
DNS zone
blogspot.com

Location

IP address
2a00:1450:4001:c13::84
ASN
15169
Organization
Google LLC
City
Frankfurt am Main
Country
DE

TLS certificate

Issuer
Google Trust Services / WE2
Subject
misc-sni.blogspot.com

DNS records

A
  • 142.251.127.132
AAAA
  • 2a00:1450:4001:c13::84
CNAME
  • blogspot.l.googleusercontent.com

DNSSEC

DS record
Yes
RRSIG
No
DNSKEY
Yes

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
1; mode=block
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a00:1450:4001:c13::84
IP version
6

Redirects

Redirect chain
  • https://minecrfatco.blogspot.com

Technology stack

Technologies
  • Blogger
  • Sentry
  • Python
  • Java
  • OpenGSE
  • Google Hosted Libraries
  • jQuery
  • Google Analytics
  • Cloudflare Rocket Loader
  • CPABuild
  • Open Graph
  • HTTP/3

HTTP headers

Response headers
Server
GSE
Content-Type
text/html; charset=UTF-8
X-Content-Type-Options
nosniff
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 1; Domain: blogspot.com; Issuers: pki.goog
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-09T13:09:10Z; First: 2026-11-09T13:09:10Z; Changes: 0; Days archived: 1; Avg page bytes: 11553
Trackers
Requests: 16; Trackers: (Name: Amazon CloudFront; Company: Amazon; Country: US; Category: Hosting; Requests: 11), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Static; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: Google Analytics; Company: Google; Country: US; Category: Site Analytics; Requests: 1), (Name: Sentry; Company: Sentry; Country: US; Category: Utilities; Requests: 1)
Forms and mixed content
No sri: https://d9qn9uafc7mxn.cloudfront.net/89adedd.js, https://ajax.googleapis.com/ajax/libs/jquery/2.2.4/jquery.min.js; Third party scripts: 3
Status
Up: ✓; Code: 302; Timings: DNS: 6; TLS: 26; Wait: 401; Connect: 9; Download: 0; Response ms: 442
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
DNS server
NS: (IP: 216.239.34.10; Host: ns2.google.com), (IP: 216.239.32.10; Host: ns1.google.com), (IP: 216.239.36.10; Host: ns3.google.com), (IP: 216.239.38.10; Host: ns4.google.com); Zone: blogspot.com
Location
IP: 2a00:1450:4001:c13::84; ASN: 15169; Org: Google LLC; City: Frankfurt am Main; Country: DE
SSL
Issuer: Google Trust Services / WE2; Subject: misc-sni.blogspot.com
DNS records
A: 142.251.127.132; Aaaa: 2a00:1450:4001:c13::84; Cname: blogspot.l.googleusercontent.com
Dnssec
Ds: ✓; Rrsig: ✗; Dnskey: ✓
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: 1; mode=block; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 2a00:1450:4001:c13::84; Family: 6
Redirects
Chain: https://minecrfatco.blogspot.com
Tech stack
Technologies: Blogger, Sentry, Python, Java, OpenGSE, Google Hosted Libraries, jQuery, Google Analytics, Cloudflare Rocket Loader, CPABuild, Open Graph, HTTP/3
HTTP headers
Headers: Server: GSE; Content type: text/html; charset=UTF-8; X content type options: nosniff

Questions about minecrfatco.blogspot.com

Is minecrfatco.blogspot.com legit?

PhishDestroy rates minecrfatco.blogspot.com as critical risk (evidence score 80/100) from the recorded evidence; it was first recorded on 2026-11-09. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is minecrfatco.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 minecrfatco.blogspot.com. A confirmed blockchain transaction cannot be reversed.

What should I do if I used minecrfatco.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 (6)

All capture links and hashes (6)

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
Google Safe Browsing Flagged Social engineering checked 2026-11-22
IP Reputation Germany192.178.183.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. 24 reports PhishingEmail SpamPort ScanHacking checked 2026-11-09 last reported
Platform provider blogspot.com
Hosting abuse contact abuse@google.com, network-abuse@google.com Google LLC · AS15169
HTTP Status404 Not Found
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-11-09
DOM Analysisanalyzed 2026-11-09score 10/1002 brand signals
Submitted URLhttps://minecrfatco.blogspot.com/
Observed page title
Minecraft Coins Generator
Automated brand references
Google Minecraft
TLS Certificate
Issued by WE2 · stored validity ends in 38 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Germany192.178.183.132
Network ASN
AS15169
AS name
GOOGLE - Google LLC, US
Organization
Google LLC
Observed location
GermanyFrankfurt am Main, DE
Server header
GSE

Nameservers 1

  • ns4.google.com

Location describes the IP network.

TLS certificate

Issuer
WE2
Valid from
2026-10-07 19:08:52
Valid until
2026-12-30 19:08:51
Hostname match
No
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 10 SANs
  • misc-sni.blogspot.com
  • blogspot.ae
  • *.blogspot.ae
  • blogspot.al
  • *.blogspot.al
  • blogspot.am
  • *.blogspot.am
  • blogspot.ba
  • *.blogspot.ba
  • blogspot.be

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:19 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:19 UTC
RDAP registration
Observed timeline last reachable: 2026-11-10 00:38 UTC last content: 2026-11-10 00:38 UTC current episode first observed: 2026-11-10 12:04 UTC observed RIP window: 2026-11-10 00:38 UTC → 2026-11-10 12:04 UTC · 11.43h midpoint estimate ≈ 2026-11-10 06:21 UTC · precision medium · basis bounded
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 · 9 identified
Open complete records

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 78

Google PageSpeed Insights — mobile performance audit of minecrfatco.blogspot.com ·

78
Needs Work
Performance
FCP
1.83 s
First Contentful Paint
LCP
4.7 s
Largest Contentful Paint
CLS
0.038
Cumulative Layout Shift
TBT
15 ms
Total Blocking Time
SI
4.88 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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: https://minecrfatco.blogspot.com/
Minecraft Coins Generator
Minecraft Coins Generator
Response
HTTP 200
HTML body
53.0 KB
Compressed
10.8 KB
Links
0 internal · 0 external
Detected technologies
jquery
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0
Content-Encoding: gzip
Server: GSE
Security headers present
Content-Security-PolicyX-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: Minecraft Coins Generator
Open Graph description: Minecraft Coins Generator
Saved response-header values · 15
Alt-Svc
h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Cache-Control
private, max-age=0
Content-Encoding
gzip
Content-Security-Policy
upgrade-insecure-requests
Content-Security-Policy-Report-Only
default-src https: blob: data: 'unsafe-inline' 'unsafe-eval'; report-to blogspot; report-uri https://www.blogger.com/cspreport
Content-Type
text/html; charset=UTF-8
Date
Mon, 09 Nov 2026 13:07:59 GMT
Etag
W/"fea4bc77eaa5ce32ff7cd03fd020bc5fb609f2f0231be10bed04db9e01232432"
Expires
Mon, 09 Nov 2026 13:07:59 GMT
Last-Modified
Thu, 29 Aug 2024 19:01:53 GMT
Report-To
{"group":"blogspot","max_age":2592000,"endpoints":[{"url":"https://www.blogger.com/cspreport"}]}
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 details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.43
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data110
Open complete records

Captured network requests

Network requests: 28 SHA-256 hashes: 28 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-09 13:13 UTC.

Open this scan on URLScan 01a1c06c-3469-70bc-b32f-368407a2524a ↗

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
Minecraft Coins Generator
Crawler
Blog not found
minecrfatco.blogspot.com
Stored observation history15
Open complete records
All retained availability observations46
Open complete records

Threat Response Pipeline

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

Recorded events: 10. 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
    minecrfatco.blogspot.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Google Safe Browsing · Automated brand label: Minecraft · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published recorded

Recorded activity

4 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+9596 d 15 h
  1. Google Safe Browsing

    Threat flag recorded

    +12 d 15 h
  2. Wayback Machine

    Page archived

    same minute
  3. Added to PhishDestroy

    minecrfatco.blogspot.com

    same minute
  4. URLScan

    Page captured

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