Security engines reporting a detection: 3. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Network Security Intelligence Registrar context
Registrar contextNiceNIC
Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
PhishDestroy has placed revenue-xstcks.com on its internal blocklist as a suspicious domain. The domain was first observed by PhishDestroy on 2026-10-19. No page title was recorded at the time of observation.
How the scam works
The available detections and blocklist entries indicate that the site may be used for malicious purposes, but no specific technique such as phishing, credential harvesting, or malware delivery has been observed on this page. Listings of this type often arise from reports of fraudulent or abusive behavior, yet the exact mechanism cannot be confirmed without further evidence.
Evidence
VirusTotal reported three detections from 92 engines on 2026-10-19, with Forcepoint ThreatSeeker, Fortinet and Gridinsoft flagging the domain. Google Safe Browsing checked the domain on 2026-10-19 and did not flag it. The external blocklist ScamSniffer listed the domain on 2026-10-19, and PhishDestroy’s internal list also contains it as of the same date. Spamhaus DBL marked the domain as spam on 2026-10-19. OTX recorded three pulses referencing the domain on 2026-10-19.
Infrastructure
The domain was registered on 2026-10-11 through NICENIC INTERNATIONAL GROUP CO., LIMITED. Hosting records show the domain resolving to IP 188.114.97.3, which belongs to CloudFlare, Inc. and is recorded in Canada. Registration date does not imply launch date, and the CDN address does not reveal the origin server’s location.
What to do
Visitors should avoid entering any credentials or personal information on the site; if any data was submitted, change associated passwords and monitor accounts for unusual activity. Defenders should block revenue-xstcks.com at the network perimeter, add the exact IP address to monitoring rules, and note its presence on Spamhaus and external blocklists for future threat‑intel correlation.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Infrastructure map · revenue-xstcks.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.
4 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 revenue-xstcks.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.
(RU)
PhishDestroy Investigation
