PhishDestroy first recorded fission-drive.com on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-19 11:55 UTC. Retrieved (as stored): 2026-10-26 23:14 UTC.
Page title: “fission-drive.com”
More about the sources
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-19 11:55 UTC. Retrieved (as stored): 2026-10-26 23:14 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@porkbun.com. The latest stored availability evidence still shows the domain reachable; 26 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
Elapsed since first report
26 days
Reports sent
1
Latest case ID
PD-20261026-046C7B
Current status
HTTP 200 at latest stored check
Analysis
Domain summary
PhishDestroy first recorded fission-drive.com on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-19 11:55 UTC. Retrieved (as stored): 2026-10-26 23:14 UTC. Risk: critical (evidence score 100/100). Registrar: Porkbun. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.
PhishDestroy added fission-drive.com to its internal blocklist on 2026-10-26 under a trusted‑auto rule that flags domains with prior security signals. The site returned an HTTP 200 status when checked on that date, while the page fetch recorded a 403 response and no page title was observed.
How the scam works
The detections associated with this domain are typical of phishing or malware distribution campaigns, but no specific malicious payload or credential‑harvesting form was observed on the captured page. Consequently, the listing reflects a general risk category rather than a confirmed exploit.
Evidence
VirusTotal scanned the domain on 2026-10-19 and reported 17 detections from 92 engines, including 14 malicious and 3 suspicious labels from vendors such as BitDefender, ESET and Forcepoint ThreatSeeker. Google Safe Browsing checked on 2026-10-27 and did not flag the domain. URLScan captured the site on 2026-10-26; its engine verdict marked it malicious with a score of 49, while the overall verdict was non‑malicious. Cloudflare Radar scanned on 2026-10-27 and returned a malicious verdict, categorising the domain as malware. OTX listed five pulses referencing fission-drive.com as of 2026-10-27, and PhishDestroy’s internal blocklist marks the domain as malicious while external blocklists showed no entries at the time of checking.
Infrastructure
The domain was registered with Porkbun LLC on 2025-11-18, making it 342 days old at the time of observation. Recorded DNS data showed A records pointing to 188.114.96.3 and 188.114.97.3 and AAAA records to 2a06:98c1:3120::3 and 2a06:98c1:3121::3, hosted on the Cloudflare network in the United Kingdom. The TLS certificate observed on 2026-10-27 was issued by Google Trust Services, covered fission-drive.com and its subdomains, and was valid from 2026-09-11 to 2026-12-10; DNSSEC was not enabled.
What to do
Visitors should avoid entering any credentials, downloading files, or interacting with the site, and should change passwords if any information was submitted. Defenders should block fission-drive.com at the network perimeter, monitor logs for connections to the recorded IP addresses, and add the domain to threat‑intelligence feeds for continued observation.
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.
Urlscan result at: 2026-10-27 05:31:03; Urlscan enriched at: 2026-10-27 10:17:32
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
fission-drive.com — Suspicious Domain
AI description
PhishDestroy listed fission-drive.com as a suspicious domain after multiple detections, including VirusTotal and Cloudflare Radar alerts.
AI summary
Overview PhishDestroy added fission-drive.com to its internal blocklist on 2026-10-26 under a trusted‑auto rule that flags domains with prior security signals. The site returned an HTTP 200 status when checked on that date, while the page fetch recorded a 403 response and no page title was observed. How the scam works The detections associated with this domain are typical of phishing or malware distribution campaigns, but no specific malicious payload or credential‑harvesting form was observed on the captured page. Consequently, the listing reflects a general risk category rather than a confirmed exploit. Evidence VirusTotal scanned the domain on 2026-10-19 and reported 17 detections from 92 engines, including 14 malicious and 3 suspicious labels from vendors such as BitDefender, ESET and Forcepoint ThreatSeeker. Google Safe Browsing checked on 2026-10-27 and did not flag the domain. URLScan captured the site on 2026-10-26; its engine verdict marked it malicious with a score of 49, while the overall verdict was non‑malicious. Cloudflare Radar scanned on 2026-10-27 and returned a malicious verdict, categorising the domain as malware. OTX listed five pulses referencing fission-drive.com as of 2026-10-27, and PhishDestroy’s internal blocklist marks the domain as malicious while external blocklists showed no entries at the time of checking. Infrastructure The domain was registered with Porkbun LLC on 2025-11-18, making it 342 days old at the time of observation. Recorded DNS data showed A records pointing to 188.114.96.3 and 188.114.97.3 and AAAA records to 2a06:98c1:3120::3 and 2a06:98c1:3121::3, hosted on the Cloudflare network in the United Kingdom. The TLS certificate observed on 2026-10-27 was issued by Google Trust Services, covered fission-drive.com and its subdomains, and was valid from 2026-09-11 to 2026-12-10; DNSSEC was not enabled. What to do Visitors should avoid entering any credentials, downloading files, or interacting with the site, and should change passwords if any information was submitted. Defenders should block fission-drive.com at the network perimeter, monitor logs for connections to the recorded IP addresses, and add the domain to threat‑intelligence feeds for continued observation. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17a5c-c4be-7776-a06b-84b414b04c12/ Cloudflare Radar report: https://radar.cloudflare.com/scan/50e0fde1-f796-4bf2-a650-cddcfbfe377e URLQuery report: https://urlquery.net/report/7812b862-3f8c-4cbb-9cb0-6f61857b34ad Stored capture screenshot: https://i.ibb.co/w3RQtqc/af614cc6c5bf.png Cloudflare Radar screenshot (2026-10-26T23:15:30Z): https://screenshots.phishdestroy.io/cf/50e0fde1-f796-4bf2-a650-cddcfbfe377e.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/7812b862-3f8c-4cbb-9cb0-6f61857b34ad.png URLScan screenshot (2026-10-26T22:20:33Z): https://screenshots.phishdestroy.io/us/01a17a4c-93a5-7215-bcb1-007e2eaa69ca.png URLScan capture report: https://urlscan.io/result/01a17a4c-93a5-7215-bcb1-007e2eaa69ca/ VirusTotal report: https://www.virustotal.com/gui/domain/fission-drive.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=fission-drive.com Archived copy: https://web.archive.org/web/20261026223917/https://fission-drive.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
The Tranco rank (how much traffic) is rather low The age of this site is (very) young. This website was reported by IPQS for phishing. This website has been classified as suspicious by IPQS
We found a valid SSL certificate DNSFilter labels this site as safe
Network Security Intelligence
Cloudflare Radar VerdictMalicious
Security threats Malware Malware
Questions about fission-drive.com
Is fission-drive.com legit?
PhishDestroy rates fission-drive.com as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 14. Suspicious: 3. Analysis time (as stored): 2026-10-19 11:55 UTC. Retrieved (as stored): 2026-10-26 23:14 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is fission-drive.com safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on fission-drive.com. A confirmed blockchain transaction cannot be reversed.
What should I do if I used fission-drive.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.
Issued by Google Trust Services / WE1· stored validity ends in 18 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
London, GB
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
elisabeth.ns.cloudflare.com
grant.ns.cloudflare.com
SOA
nsname: elisabeth.ns.cloudflare.com
hostmaster: dns.cloudflare.com
serial: 2416162827
refresh: 10000
retry: 2400
expire: 604800
minttl: 1800
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-09-11 22:02:46
Valid until
2026-12-10 23:01:25
Hostname match
Yes
Validity
Within stored validity dates
Collection time
2026-10-26 23:02 UTC
Collection source
PhishDestroy collector
Certificate fingerprint8bb8218c0b46aad98d7f41cdfafc72a6400b75a320e40b77cb550e295e56448cCertificate names · 2 SANs
fission-drive.com
*.fission-drive.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Resolved
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:16 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:16 UTClast content: 2026-11-22 11:16 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.
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-10-29 01:56 UTC.
Recorded events: 16. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
8 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+335 d 3 h
Added to PhishDestroy+7 d 10 h
First abuse report sent+3 min
Reported 342 d 13 h after registration
AlienVault OTX
5 community references
same minute
Cloudflare Radar
Phishing
+29 min
Porkbun
Asked for a report through its web form
+4 min
Abuse report sent
PD-20261026-046C7B · Receipt 83553
abuse@porkbun.com
+2 min
Wayback Machine
Page archived
same minute
Added to PhishDestroy
fission-drive.com
same minute
URLScan
Page captured
+7 d 10 h
VirusTotal
17/92 engine detections
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
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
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.
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 fission-drive.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)
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
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.