whatsapp.imake-app.com appeared on PhishDestroy's blocklist on 2026-10-19. The site mimics the WhatsApp brand and is likely aimed at WhatsApp users seeking to verify or log in. Its current operational status is unknown, and it has been flagged solely by PhishDestroy at this time.
How the scam works
The page appears to lure visitors into providing personal data such as phone numbers, verification codes, or WhatsApp login credentials. By capturing these details, attackers can hijack accounts, send malicious messages, or use the information for broader social‑engineering attacks. No specific malicious kit or payment flow is observed, but the risk is the loss of account control and potential downstream fraud.
Evidence
VirusTotal scanned the domain on 2026-10-19 and reported 0 detections out of 92 scanning engines, indicating no known malware signatures. The only independent listing is PhishDestroy's blocklist. No detections from Google Safe Browsing, urlscan.io, or Spamhaus are available, so the classification relies on the domain's brand impersonation and its presence on our blocklist.
Infrastructure
The site resolves to IP address 104.21.18.161, which is the only hosting detail available. No registrar, TLS certificate issuer, or additional hosting metadata are provided, limiting insight into the operator’s infrastructure. The domain was first observed on 2026-10-19, suggesting it was active for a short period before detection.
What to do
Anyone who visited the site should immediately stop entering any WhatsApp credentials, change their WhatsApp password, and enable two‑factor authentication if not already active. Review linked accounts for unauthorized activity. Security teams should block the domain at the network perimeter, add it to internal blocklists, and monitor for any related phishing attempts targeting WhatsApp users.
Registration (base domain)imake-app.com · Created Nov 16, 2022 —Expires Nov 16, 2026
Technical detailsProvenance & timestamps
First DetectedOct 19, 2026
Submitted URLhttps://whatsapp.imake-app.com/
Favicon Hash
Case ID
TLS Certificate
Issued by Let's Encrypt / YE2· stored validity ends in 87 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.67.182.187
Edge-IP reputation is not attributed to this domain.
Nameservers 2
alberto.ns.cloudflare.com
poppy.ns.cloudflare.com
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-16 22:50:38
Valid until
2027-01-14 22:50:37
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-19 13:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfb89e4c277a9acef775120c090307feab1509b6353a0d132b19b4fe2e4921f2dCertificate names · 1 SANs
imake-app.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
3 evidence signal groups linked0 stored notification recordsUnverified
Listed domains receive at least one abuse report; this entry has no retained notification history.
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 whatsapp.imake-app.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.
(US)
