Open Bug 2062794 Opened 3 months ago Updated 1 month ago

Copy Clean Link: Strip Temu tracking parameters on www.temu.com

Categories

(Core :: Privacy: Anti-Tracking, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: dmehic, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: good-first-bug)

Temu is absent from both strip-on-share lists, so Copy Clean Link does nothing on Temu URLs. Because canStripForShare returns false, the menu item is not even offered.

Temu product URLs carry their entire identity in the path so the whole query string is arguably disposable.

What the parameters leak

Parameter Content
_x_sessn_id Session ID — links the recipient's visit back to the sharer's session
refer_page_id 10005_1786482311059_21bs7cja0q — millisecond timestamp plus a random token
refer_page_sn, refer_page_el_sn, refer_page_name Originating page and the element clicked (home)
_oak_mp_inf Opaque base64 tracking blob
_oak_gallery_order Five IDs describing the sharer's personalised gallery ordering
_oak_rec_ext_1 Recommendation-engine context (MTI3Nw decodes to 1277)
freesia_scene, _oak_freesia_scene Internal scene / experiment tracking
spec_gallery_id Redundant — identical to the product ID already present in the path
top_gallery_url Nested img.kwcdn.com CDN URL, not needed to load the page

The first two matter most: a session ID and a timestamped page ID pasted into a group chat are exactly the cross-user linkage this feature exists to prevent.

Proposed rule

Add to StripOnShareLists/MPL2/StripOnShare.json:

"temu": {
  "queryParams": [
    "_oak_mp_inf", "_oak_freesia_scene", "_oak_rec_ext_1", "_oak_gallery_order",
    "_x_sessn_id", "freesia_scene", "refer_page_el_sn", "refer_page_id",
    "refer_page_name", "refer_page_sn", "spec_gallery_id", "top_gallery_url"
  ],
  "origins": ["www.temu.com"]
}

Prototyped locally and verified against nsIURLQueryStringStripper: canStripForShare becomes true and the URL strips from 706 to 214 characters, leaving just the product path. The stripped URL was confirmed to still resolve (HTTP 200, with 601100689088857 present in the response).

Notes for whoever picks this up

  • origins is www.temu.com only. temu.com returns a 301 to www.temu.com, and origin matching is exact-host with no wildcard or eTLD+1 fallback. Since Firefox displays the post-redirect host, a bare temu.com entry would never match anything and would be dead weight.
  • Parameter matching is exact-name, case-insensitive, with no prefix wildcards. Temu uses a wide _oak_* family and the twelve above come from a single URL. Please collect parameters from several page types first — product page, search results, category listing, and a link produced by Temu's own share sheet — rather than landing only this sample.
  • The LGPL list does not need touching. temu is a new key in neither file, so there is no cross-file parameter collision (see bug 2062660 comment 1 for why that matters).
  • Validate with ./mach test toolkit/components/antitracking/test/xpcshell/test_validate_strip_on_share_list.js.
Severity: S3 → N/A
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.