VirusTotal
2 / 92 engine detections
Open report“Box in Black | BlackBox Store”
2 / 92 engine detections
Open reportMalicious
Open report3 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
blkbx.shop presents itself as a BlackBox Store online retailer. The page title "Box in Black | BlackBox Store" tries to mimic a legitimate brand. PhishDestroy first recorded the site on 2026-10-17. As of 2026-10-19 the domain is alive and returns a reachable redirect.
Visitors are shown product listings under the BlackBox Store name and are prompted to complete purchases with cryptocurrency or card payments. After payment the site never delivers any goods, effectively stealing the funds. The fake‑shop kit relies on a convincing storefront and the lure of discounted items to extract money from shoppers.
VirusTotal flagged the domain in 2 of 92 scanning engines, with alphaMountain.ai and CyRadar reporting it as malicious. urlscan.io returned a malicious verdict and explicitly flagged the site as a fake shop. PhishDestroy lists the domain on its blocklist and OTX has three pulses referencing it. No additional detections from Google Safe Browsing or Spamhaus were reported.
The domain was registered on 2026-07-26 through Dynadot Inc., giving the operators roughly three months before PhishDestroy’s first sighting. Hosting is provided by Malakmadze Web LLC in the United States, reachable at IP 212.52.28.20. The site uses a Let’s Encrypt / YE2 TLS certificate, which is common for short‑lived malicious sites.
Anyone who entered payment details should immediately halt any pending crypto transfers, monitor wallet activity, and report the loss to the relevant exchange or financial institution. Change passwords used on the site and enable two‑factor authentication wherever possible. Security teams should add blkbx.shop to web filters, monitor for similar domain registrations, and share indicators of compromise with threat‑intel communities.
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP reputation is not attributed to this domain.
mcgrory.ns.cloudflare.comLocation describes the IP network.
366f2f0f721396770216d35d0faa2c660380d590830381ab50245e8f062d7555Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://blkbx.shop/https://blkbx.shop/Content-Encoding: gzipContent-Type: text/plain;charset=UTF-8h3=":443"; ma=2592000gziptext/plain;charset=UTF-8Sat, 17 Oct 2026 20:22:54 GMTstrict-origin-when-cross-originchunkedAccept-Encoding1.1 CaddynosniffSAMEORIGIN1; mode=blockValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
1→2
Unknown→redirected
http_redirect
0→1
Unknown→redirected
http_redirect
3 community references
View sourceNo threat flag
View source2/92 engine detections
View sourceblkbx.shop
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
blkbx.shop
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
blkbx.shop)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.