A sponsored search result served an installer, but the same link now shows the vendor's real page - why?
answer
- the URL is a function, not a place
- the redirector decides per request
- review traffic must see something innocuous
- every click is billed to the operator
- the paid slot outranks the real result
basics
~20 sThe advertisement's click-through URL points at a redirector the operator controls. It inspects the visitor - address, geography, user agent, referrer, whether they have been seen before - and hands non-matching visitors the genuine page. One URL, two destinations.
solid answer
~50 sBecause the destination is a function of the visitor, not a fixed address. The paid chain is: an advertiser account bids on the product name, the creative displays a plausible URL, and its click-through goes to a redirector the operator owns. That redirector decides per request - source address range and network, geography, operating system and user agent, referrer, time since the click, whether a cookie from an earlier visit is present - and only matching visitors reach the download page. Everyone else is bounced to the real project site. Two motives drive it: the advertising network's review and any casual re-check must see something innocuous so the account survives, and every click is paid for, so the operator does not want to pay for visitors who cannot become victims. The practical consequence is that opening the link yourself is not a test. Same URL, different visitor, different answer.
code
text · 11 lines# sponsored slot for a search on a Kubernetes command-line tool
GET /promo?kw=k8s-cli-install -> 302 Location: https://trk.adclick[.]example/c/9f2
# visitor A: consumer address, Windows, matches the campaign filter
GET /c/9f2 src=203.0.113.44 UA=Windows Accept-Language=en-GB
-> 302 Location: https://k8s-cli-tool-download[.]example/get # installer offered
# visitor B: datacentre address, Linux, no referrer
GET /c/9f2 src=198.51.100.9 UA=Linux Referer=-
-> 302 Location: https://<genuine project site>/docs/install # real page
...go deeper
Know that a sponsored slot sits above the genuine result and that whoever pays can appear first, so being top of the page is not evidence of being the real project.
Explain the four-part chain - account and bid, creative, redirector, download page - and name the signals a redirector cloaks on: source network, geography, user agent, referrer, repeat visits.
Show why a re-visit is not a test and be able to state exactly what a single clean visit does and does not establish, and why the hostnames rotate while the behaviour does not.
Be ready to argue what an organisation does about people sourcing tools from open search at all, and who owns and funds the alternative your engineers would actually use.
## The plumbing, named A malvertising route has four parts and it helps to keep them separate: 1. **The account and the bid.** The operator opens an advertiser account and bids on the query people type when they want a specific tool - typically the product's own name, or `install <tool>`. Buying the brand's own name is legal, ordinary practice and cheap for niche terms. 2. **The creative.** What the searcher sees. The display string can be made to look like the real project's address while the click-through goes somewhere else entirely; the visual slot sits *above* the genuine organic result, so the attacker is the first thing on the page. 3. **The redirector.** A host the operator controls that receives every click and decides where to send it. This is where cloaking lives. 4. **The landing page.** A convincing download page whose only job is to offer a file. The SEO-poisoned variant swaps part 1 and 2 for content engineered to rank organically - long-tail installation queries, bulk-generated pages, or posts on compromised legitimate sites - and keeps parts 3 and 4 unchanged. Paid placement is instant and precisely keyword-targeted; ranking is free but slow and can be outranked. Operators use both. ## Why cloak at all Cloaking is not subtlety for its own sake; it is two concrete costs. - **Account survival.** Advertising platforms review creatives and destinations, and the review traffic is recognisable - it comes from the platform's own networks, at odd hours, often from a datacentre address with no referrer. If that reviewer is handed the genuine project site, the campaign is approved and keeps running. The account is the operator's inventory, and it costs money and identity documents to replace. - **Click spend.** Every click is billed. A visitor whose address sits in a hosting provider's range, or whose language and platform do not match the campaign, is unlikely ever to run the installer. Serving them the real site costs nothing and saves the operator from paying for a visit twice over. That second point is the giveaway about the class of operator behind this. Someone paying per click, bidding on a generic tool name, indifferent to which organisation the clicker works for, is running a commodity operation on bought infrastructure - a kit, an ad account, a redirector service. Contrast that with an operator who poisons a single sector's association page and waits: that one is buying a *specific readership* and paying in effort rather than in clicks. ## What the cloaking does to your reasoning The important consequence is epistemic. A URL is normally treated as a name for a destination. Behind a cloaking redirector it is not: it is a function whose arguments include your address, your platform, your language, your referrer and the time. So: - **`I opened it and it was fine` proves what that one request was handed.** It says nothing about what a colleague on a different network, on a different platform, twenty minutes earlier was handed. - The reverse also holds. A visitor who *was* served the installer is not contradicted by the page looking clean afterwards, and the campaign may simply have finished its budget for the day. - The chain is disposable by design. The redirector hostname, the landing hostname and the ad account are all cheap and rotate constantly; the *behaviour* - bid on the tool name, cloak, offer an installer - is what persists across campaigns. ## Why the search result is such a good position There is a piece of standard advice that this technique feeds on directly: **do not click links in messages - type the name into a search engine instead.** That advice is sound against message-based lures and it delivers the searcher straight into a slot the attacker has bought above the real answer. The person did everything they were told, chose the destination themselves, and chose the attacker's. It is also worth being precise about what was *not* involved: no defect in the browser, no defect in the search engine, no defect in the advertising platform. Buying a keyword and running a redirector are the platform working as designed. The only irregular thing is the file at the end.
- Why pay per click at all when a poisoned organic result costs nothing?Speed and placement. A bid puts the operator above the genuine result the same day, against exactly the query they choose. Ranking organically takes weeks, can be outranked, and cannot be aimed as precisely. Clicks on a niche tool name are cheap enough that the arithmetic works, and the two are often run together.
- What does the cloaking behaviour tell you about the operator's economics?That they are paying for volume and are indifferent to who lands. Filtering out hosting-provider addresses and mismatched platforms is a cost-control measure, which is a commodity-operation signature: bought ad account, bought kit, disposable hostnames. An operator buying a specific readership instead would pay in effort and would filter for identity, not for value-per-click.
- How does this route differ from a compromised distribution mirror serving the same tool?In who chooses. Here a human searched, saw a paid slot and picked it, and the genuine project distribution was never touched. A poisoned mirror or namespace sits inside an automated path where nobody chooses anything, reaches every consumer of that artefact, and is a different family of problem entirely.
saying these in an interview costs you the question
- Treats revisiting the URL as a valid test
- Assumes the advertising platform was compromised
- Believes the displayed URL is the destination
- Says the searcher must have mistyped the name
- Confuses this with a tampered official mirror