treasurystellar.com is a Ledger impersonation page detected by PhishDestroy on 2026-10-23. Risk: high (66/100). Registrar: TUCOWS.COM, CO. Status: Last known active. Hosting: Podaon SIA. Do not enter credentials or connect a wallet.
“Treasury Bank — The QFS Era Has Begun”
Registrar
TUCOWS.COM, CO
Resolved IP
212.43.155.227
Registered
Oct 16, 2026
PhishDestroy assessment
High66/100Evidence score
Availability
Last known activeLatest stored reachability observationObserved · HTTP probe
Risk signals
Stored blocklist matches: 2Automated brand label: LedgerYoung domain: 7 days old
PhishDestroy listed treasurystellar.com on 2026-10-23 after an admin report noting the domain was only six days old. The recorded page title reads "Treasury Bank — The QFS Era Has Begun". An initial AI assessment on the same day could not determine the page content, marking the verdict as unknown. An HTTP 200 response was observed on 2026-10-23, confirming the site was reachable at that time.
How the scam works
No specific malicious mechanism was observed on this page, so the listing does not confirm a particular fraud type. Generally, newly registered domains that present financial‑themed branding may attempt impersonation, phishing, or fraudulent investment offers to lure visitors into disclosing credentials or sending funds. The page’s claim of a "Treasury Bank" and reference to the QFS era fits that broader pattern, but no concrete request or malicious behavior was captured.
Evidence
VirusTotal scanned the domain on 2026-10-23 with 92 engines and reported 0 detections. Google Safe Browsing checked on 2026-10-23 and did not flag the site. External blocklists MetaMask and SEAL listed the domain (2 listings) on 2026-10-23. OTX recorded 4 pulses mentioning the domain on the same date. PhishDestroy’s internal blocklist marked it as true on 2026-10-23. urlscan.io captured the site on 2026-10-23; its engine score was 99 (malicious) but the overall verdict was non‑malicious with a score of 0, and a 307 redirect to HTTPS was noted.
Infrastructure
The domain was registered on 2026-10-16 through Tucows Domains Inc. The authoritative nameservers are 1-you.njalla.no, 2-can.njalla.in, and 3-get.njalla.fo. The recorded IP address is 212.43.155.227, belonging to Podaon SIA in the Netherlands. TLS was provided by Let’s Encrypt, valid from 2026-10-20 to 2027-01-18. Open ports observed include 22, 80, and 443. DNSSEC is not enabled.
What to do
Visitors should not enter credentials, private keys, or financial information on this site; if they have, change passwords and monitor accounts for unauthorized activity. Defenders should add treasurystellar.com and its IP address to blocklists, review server logs for connections, and enforce outbound traffic controls to the recorded host. Continue monitoring for any future changes in content or reputation.
{
"title": "Treasury Bank — The QFS Era Has Begun",
"themeColor": "#07182b",
"description": "Explore Treasury Bank: QFS settlement rails, transparent ledgers, TRSY and XLM."
}
No. PhishDestroy classifies treasurystellar.com as a Ledger impersonation page (risk: high, 66/100); it was first detected on 2026-10-23. Treat the site as unsafe.
Is treasurystellar.com safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on treasurystellar.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used treasurystellar.com?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Issued by Let's Encrypt / YE2· stored validity ends in 87 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
212.43.155.227
Network ASN
AS211381
Organization
Podaon SIA
Observed location
Oude Meer, NL
Server header
nginx/1.24.0 (Ubuntu)
Nameservers 3
1-you.njalla.no
2-can.njalla.in
3-get.njalla.fo
Location describes the IP network.
TLS certificate
Issuer
Let's Encrypt / YE2
Valid from
2026-10-20 20:39:02
Valid until
2027-01-18 20:39:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint69cf894b7e2d9ba39848d18e76f9e99357ebdd9dce1903fb87d98192ec99f13bCertificate names · 1 SAN
treasurystellar.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
4 evidence signal groups linked0 stored notification recordsLast known active
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 treasurystellar.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.
(KN)
