uberrichinfatcity.com
159.203.141.19AS14061 · USthis page loaded a hidden, encoded shell command
- Browser Analysismalicious
- Threat Intelligencemalicious
- Content Inspectionclean
- Network & Hostingclean
- Related Infrastructureclean
- Domain Intelligenceunknown
- TLS Fingerprintunknown
What happened
Step by step, from what the scanner recorded.Dangerous — confirmed threat
AutomatedIt is listed on external threat-intelligence feeds. We found strong evidence that this site is malicious — for example a phishing page, a scam, or hostile code. Treat anything it asked for (passwords, card details, codes) as exposed.
What to do
Do not enter any information or download anything. If you already did, change those passwords now and contact your bank if payment details were involved. Block or report the link to your team.
This reflects the evidence found at the time of the scan. If you believe it is a mistake, you can escalate it for analyst review.
Findings
Strongest firstThe lure never opened for us — it sits where our click could not reach it. We decoded the command out of the page's own code instead, in bytes this scan fetched: https://idcool.codes/api.php?s=a3946e3ded820e3d2f02885bf63c8a3a176d58bb9403b402&_v=29840969
Live attacker command — do not run this
This is the exact text the page instructs a visitor to run. Pasting it into the Windows Run dialog (Win+R), PowerShell, or any terminal will execute the attacker's payload on your machine. Urlyze decoded it out of the page's own code and never executed it.
Command recovered from bytes this page loaded, not from a clipboard: it was hidden under more than one decode inside those bytes, and this is the road it came down: arr^21>b64>xor^18 (https://idcool.codes/api.php?s=a3946e3ded820e3d2f02885bf63c8a3a176d58bb9403b402&_v=29840969). Evidence for this sample: the response body; no instruction screenshot. Nothing was executed.
Analyst noteTreat the command as the payload — read it for the download URL, the dead-drop (Telegram/blockchain) and the execution method. Evidence for this sample is the command and the response it came from; there is no instruction screenshot, because this kit renders its lure inside an overlay frame. Nothing was executed.
The page fetched instructions from a public blockchain RPC node while showing the visitor nothing to do with crypto — no wallet, no token, no exchange. The next stage is held in a smart contract instead of on a server, so it survives domain takedowns and can be rewritten by its operator at any time. ⚠️ What this does NOT say: the contract's contents were not read, and the payload it returned — if any — is recorded separately when a later stage delivers it.
Analyst notePivot on these nodes and on the contract address in the request bodies. A page with no crypto surface has no legitimate reason to read a chain.
The page dynamically injected scripts from other domains. This is extremely common on legitimate sites (CDNs, analytics, asset domains) and is shown for context only.
Analyst noteNoisy by itself — a CDN/asset domain (e.g. a brand's own *.githubassets.com) is normal. Only meaningful if the source domain is unrelated/suspicious.
Infrastructure
- IP
- 159.203.141.19DIGITALOCEAN-ASN - DigitalOcean, LLC, US · AS14061US
- TLS
- CN=YR1, O=Let's Encrypt, C=US · expires Dec 9, 2026
WHOIS
- Registrar
- GoDaddy.com, LLC
- Created
- Jan 7, 2020
- Expires
- Jan 7, 2027
- Nameservers
- ns43.domaincontrol.comns44.domaincontrol.com
Hashes & fingerprints
Page capture
LiveTitle “Uber Rich in Fat City – Dancing to Remember… Dancing to Forget”
Engines
7 · time to verdictPage
- HTTP
- 200 · Completed
- Title
- Uber Rich in Fat City – Dancing to Remember… Dancing to Forget
- Load
- 5.83 s · 44 requests