Security engines reporting a detection: 7. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
PhishDestroy has added 918372-icloud.com to its internal blocklist as a suspicious domain. The site was first observed by PhishDestroy on 2026‑10‑20 and the recorded page title is “iCloud”. The domain was registered on 2026‑10‑18, two days before first observation.
How the scam works
Because the domain is flagged by multiple security engines, it may be used for typical phishing or fraud activities, but no concrete behavior was observed on the page. The listing alone does not prove a specific attack vector.
Evidence
VirusTotal scanned the domain on 2026‑10‑20 and reported 7 detections out of 92 engines, with AlphaMountain.ai, CRDF, Emsisoft, Fortinet, LevelBlue, Netcraft and SOCRadar flagging it. Google Safe Browsing checked on 2026‑10‑20 did not flag the domain. No external blocklists listed the domain as of that date, while PhishDestroy’s internal list marked it as suspicious, and OTX recorded four pulses referencing it on 2026‑10‑20.
Infrastructure
The domain was registered through CNOBIN INFORMATION TECHNOLOGY LIMITED on 2026‑10‑18. The recorded IP address for the site is 179.43.182.228.
What to do
Visitors should avoid entering Apple ID credentials or personal data on the site. If any Apple credentials were submitted, change the associated password and enable two‑factor authentication. Security teams should add the exact domain to blocklists and monitor traffic to 179.43.182.228.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.918372-icloud.comDomain record
The original observation time is not recorded for these hostnames.
Final URL:https://918372-icloud.com/signin/identifier
iCloud
Log in to iCloud to access your photos, mail, notes, documents and more. Sign in with your Apple Account or create a new account to start using Apple services.
Response HTTP 200
HTML body 621.2 KB
Compressed 200.5 KB
Links 5 internal · 0 external
Detected technologies
vuebootstrap
Selected response headers
Cache-Control: public, max-age=0
Content-Encoding: gzip
Content-Type: text/html; charset=UTF-8
X-Powered-By: Express
Security headers present
Content-Security-Policy
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 13
Accept-Ranges
bytes
Alt-Svc
h3=":443"; ma=2592000
Cache-Control
public, max-age=0
Content-Encoding
gzip
Content-Security-Policy
frame-ancestors *
Content-Type
text/html; charset=UTF-8
Date
Tue, 20 Oct 2026 13:20:06 GMT
Etag
W/"9b49d-1a1584350d5"
Last-Modified
Tue, 20 Oct 2026 07:42:49 GMT
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 Caddy
X-Powered-By
Express
Values retained by the collector; long values may be shortened during collection.
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · 918372-icloud.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same automated brand label: Apple8
Reports with the same collector label. A shared label does not establish impersonation or common ownership. View matching reports →
6 evidence signal groups linked1 stored notification recordsUnverified
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.
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 →
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 918372-icloud.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
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.
(VN)
