Skip to content

Build1 publisher2 min readPublished

A per-visit fingerprint check kept a live malware page rated clean for months

Daniel Jones of Tuxxin describes a landing page that fingerprints each visitor before it serves anything, so the reputation engines checking it from datacenter IPs recorded a harmless skeleton while real phones were handed a 148 MB installer.

The Engineer · Build desk

Photograph accompanying A per-visit fingerprint check kept a live malware page rated clean for months
Photo: thehackernews.com

What happened

  • Daniel Jones of Tuxxin says a fully authenticated Carnival Cruise Line email, booking number and all, routed real customers into malware installers and fullscreen lockers earlier in 2026.
  • Every reputation engine that checked the link rated it safe for months, and each of them looked from a single datacenter IP.
  • The landing page fingerprints the visitor per visit: scanners, command-line tools and headless browsers fail the check and get a harmless skeleton, while real browsers on real networks reach the payload.
  • The Windows branch served the PhantomJack hijacker family as forced installers of about 148 MB, signed with three-day certificates that had already expired.
  • Trinity Cyber's Tanner Piliego and Jared Grumbein documented the same redirection layer and payload family in November 2025, naming them PseudoTDS and PhantomJack.

Compiled by The EngineerSomething wrong?How this is made

Why it matters

  • constraint A reputation database keyed on a URL cannot store a property of a page that decides per visit, so the lookup inbox and browser defences depend on returns an answer good for one fetch.
  • cost Reproducing the finding costs three fetches of every link instead of one, and two of those go over residential and mobile networks a datacenter scanner does not already have.
  • exposure An installed base that accepts any version the operator offers on every launch stays reachable long after the domain and the signing certificates are dead.
  • decision Detection teams have to choose what their pipeline stores and alerts on: a verdict per URL, or the disagreement between vantage points that Jones says is the only signal a cloak produces.

The gate runs before anything malicious loads. It reads the requester, picks a branch, then serves. Jones counted four outcomes from one link and one cloaker, and says the datacenter branch was the only page any scanner reached [5]. Three of the four branches were never observed by an engine that checked [1].

That makes a verdict a record of one fetch. Under a cloak, Jones wrote, a clean verdict is a true statement about the observation and a false statement about the URL [17]. The reputation services he queried returned clean verdicts consistent with having been handed the skeleton [7]. The link reached customers through the sender's real click-tracker, on a domain that passed every email authentication check [8].

Freshness is the second problem. A cache entry keyed on a URL has to hold for as long as the entry lives, and Jones says these pages rotate what they serve between visits, so a result from last week describes a page that no longer exists [10].

His test is a comparison. Load the same URL from datacenter, residential and mobile profiles at once, then look at where they disagree [13]. Here the disagreement was blank and benign from the scanner and a forced malware download from the phone [14]. That is three fetches per link, two of them over networks a datacenter scanner does not operate [2].

Two of the packages behind the gate shipped a forced auto-update channel that checks on every launch, runs in the background, and accepts any version the operator offers [12]. Jones also describes a second layer that starts examining whoever clears the gate [19].

Now the limits. His post does not name the reputation services it checked, give a false-negative rate, or say what a multi-vantage probe costs per link [20]. urlscan.io filed the page as one of "10,000+ similar pages" [6]. That counts pages resembling this one. It is not a share of links that cloak. Trinity Cyber's victims arrived by mistyping a domain, and Jones's arrived through an authenticated marketing email [16].

So the narrow claim is the one this evidence carries: a clean result from a single datacenter IP describes that fetch, and Jones says a single datacenter IP running a headless browser is the exact profile the cloak is tuned to feed a clean page [18]. Prevalence is not established here. His screenshots of the sorting gate and of the payload are dated June 13 and June 25, 2026 [21], and he says the machinery is still running [22].

What to watch

  • Whether Trinity Cyber or another vendor publishes a prevalence figure for PseudoTDS-style sorting gates.
  • Whether any inbox or browser scanner starts fetching links over residential and mobile paths by default.
  • Whether Jones's full research writeup names the reputation services that returned clean verdicts.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories