VirusTotal
8 / 92 engine detections
Open report“Cyberpunk Auth Portal”
8 / 92 engine detections
Open reportDBL_SPAM
4 community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
carding.cm is an impersonation phishing site built around a login screen titled 'Cyberpunk Auth Portal'. Its name points to card fraud, and it presents itself as a gated sign-in page that visitors must pass through to reach whatever lies behind it. PhishDestroy first flagged it on 2026-10-07. As of 2026-10-19 the site was still online and serving its content.
Impersonation pages copy the look of a legitimate service's sign-in flow so visitors type their username, password or one-time codes into a form the operator controls. Here the bait is the 'Cyberpunk Auth Portal' screen. The page title names no specific brand, but PhishDestroy classifies the site as impersonation. Anything submitted goes straight to the operator, who can take over the matching real account, reuse the password elsewhere, or resell the login.
On 2026-10-11, 8 of 92 VirusTotal engines flagged the domain: alphaMountain.ai, Chong Lua Dao, CRDF, Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar and VIPRE. That is a minority of engines, but the vendors are independent of one another and include established web-filtering and threat-feed providers. Spamhaus lists the domain in its DBL as spam. It also appears in 4 AlienVault OTX pulses, which means other researchers have tied it to malicious activity.
The domain was registered on 2026-05-25 through Netcom.cm Sarl under Cameroon's .cm extension, about 135 days before PhishDestroy detected it. That gap fits a domain that was registered and then held for a while before being used. It resolves to Cloudflare's network in the US, so the real origin server sits behind the proxy. The Google Trust Services certificate gives the page a normal padlock, which says nothing about whether it is safe.
If you entered a username and password on this portal, change that password right away on the real service and everywhere you reused it. Then turn on app-based or hardware-key two-factor authentication. Sign out of all active sessions, check your account recovery email and phone for changes, and watch for unfamiliar logins. If you submitted card or payment details, call your bank to block the card. Defenders should block carding.cm at DNS and the proxy, search logs for users who reached it, and force credential resets for anyone who did.
urlscan.io scan and screenshot: https://urlscan.io/result/01a11484-941e-735e-8e74-17ed1700e103/
VirusTotal report: https://www.virustotal.com/gui/domain/carding.cm
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=carding.cm
Archived copy: https://web.archive.org/web/20260418031926/https://carding.cm/
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Edge-IP reputation is not attributed to this domain.
daisy.ns.cloudflare.comdavid.ns.cloudflare.comLocation describes the IP network.
f1a69e61c83f1ff00997831be4375cfc7298b0645daeb002b6b79f20e354aa3bSaved 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.carding.cmDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of carding.cm · checked Oct 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
carding.cm
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
redirected→live_content
content_served
Unknown→redirected
http_redirect
live_content→redirected
http_redirect
Unknown→live_content
content_served
Unknown→redirected
http_redirect
redirected→live_content
content_served
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
Unknown→redirected
http_redirect
live_content→redirected
http_redirect
redirected→live_content
content_served
Unknown→redirected
http_redirect
Reachable
No threat flag
View source8/92 engine detections
View source4 community references
View sourcecarding.cm
View sourcePage captured
View sourceListed 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 ↗
carding.cm)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.