我重新安装了“反应脚本”（5.0.1），作为一种依赖性的依赖性，以围绕NPM审计错误警报问题，该问题将其依赖性之一标记为严重的脆弱性。从那以后（据我所知），不仅我会得到多个“ navigator.joinadinterestgroup”和navigator.leaveadinterestgroup“ scriplet” scriplets，每当我启动前端时在控制台上奔跑（请参阅下文），但也有提到“ oupang.com”和“ outangcdn.com”
。称为“ Jridgewell/Trace-Mapping”，所以我不知道现在作为DevDectienty，这是该游戏机活动的原因，但是我找不到此软件包之间的任何关联和Coupang.com。 。
VM6:206 #%#//scriptlet("set-constant", "navigator.joinAdInterestGroup", "undefined") trace start
VM6:208 console.trace
hit @ VM6:208
VM6:210 #%#//scriptlet("set-constant", "navigator.joinAdInterestGroup", "undefined") trace end
VM6:502 #%#//scriptlet("set-constant", "navigator.leaveAdInterestGroup", "undefined") trace start
VM6:504 console.trace
hit @ VM6:504
VM6:506 #%#//scriptlet("set-constant", "navigator.leaveAdInterestGroup", "undefined") trace end
VM6:798 #%#//scriptlet("set-constant", "navigator.runAdAuction", "undefined") trace start
VM6:800 console.trace
hit @ VM6:800
VM6:802 #%#//scriptlet("set-constant", "navigator.runAdAuction", "undefined") trace end
VM6:1094 #%#//scriptlet("set-constant", "navigator.adAuctionComponents", "undefined") trace start
VM6:1096 console.trace
hit @ VM6:1096
VM6:1098 #%#//scriptlet("set-constant", "navigator.adAuctionComponents", "undefined") trace end
VM6:1390 #%#//scriptlet("set-constant", "Document.prototype.browsingTopics", "undefined") trace start
VM6:1392 console.trace
hit @ VM6:1392
VM6:1394 #%#//scriptlet("set-constant", "Document.prototype.browsingTopics", "undefined") trace end
VM6:1686 #%#//scriptlet("set-constant", "document.browsingTopics", "undefined") trace start
VM6:1688 console.trace
hit @ VM6:1688
VM6:1690 #%#//scriptlet("set-constant", "document.browsingTopics", "undefined") trace end
VM6:1982 ~coupang.com,~coupangcdn.com#%#//scriptlet("set-constant", "PartnersCoupang", "undefined") trace start
VM6:1984 console.trace
hit @ VM6:1984
VM6:1986 ~coupang.com,~coupangcdn.com#%#//scriptlet("set-constant", "PartnersCoupang", "undefined") trace end
I reinstalled "react-scripts" (5.0.1) as a devDependency to get around the npm audit false-alarm issue that flags one of its dependencies as a severe vulnerability. Starting after that (as far as I can tell) not only do I get multiple "navigator.joinAdInterestGroup" and navigator.leaveAdInterestGroup" scriplets with tracing running in my console every time I boot up my frontend (see below), but there are also mentions of a "coupang.com" and "coupangcdn.com." What is this, and how can I get rid of it? Thanks.
EDIT: As I looked into this some more, it appears that there is a react-scripts dependency called "jridgewell/trace-mapping," so I don't know if, now as a devDependency, this package is the reason for this console activity? Either way, however, I could not find any association between this package and coupang.com.
VM6:206 #%#//scriptlet("set-constant", "navigator.joinAdInterestGroup", "undefined") trace start
VM6:208 console.trace
hit @ VM6:208
VM6:210 #%#//scriptlet("set-constant", "navigator.joinAdInterestGroup", "undefined") trace end
VM6:502 #%#//scriptlet("set-constant", "navigator.leaveAdInterestGroup", "undefined") trace start
VM6:504 console.trace
hit @ VM6:504
VM6:506 #%#//scriptlet("set-constant", "navigator.leaveAdInterestGroup", "undefined") trace end
VM6:798 #%#//scriptlet("set-constant", "navigator.runAdAuction", "undefined") trace start
VM6:800 console.trace
hit @ VM6:800
VM6:802 #%#//scriptlet("set-constant", "navigator.runAdAuction", "undefined") trace end
VM6:1094 #%#//scriptlet("set-constant", "navigator.adAuctionComponents", "undefined") trace start
VM6:1096 console.trace
hit @ VM6:1096
VM6:1098 #%#//scriptlet("set-constant", "navigator.adAuctionComponents", "undefined") trace end
VM6:1390 #%#//scriptlet("set-constant", "Document.prototype.browsingTopics", "undefined") trace start
VM6:1392 console.trace
hit @ VM6:1392
VM6:1394 #%#//scriptlet("set-constant", "Document.prototype.browsingTopics", "undefined") trace end
VM6:1686 #%#//scriptlet("set-constant", "document.browsingTopics", "undefined") trace start
VM6:1688 console.trace
hit @ VM6:1688
VM6:1690 #%#//scriptlet("set-constant", "document.browsingTopics", "undefined") trace end
VM6:1982 ~coupang.com,~coupangcdn.com#%#//scriptlet("set-constant", "PartnersCoupang", "undefined") trace start
VM6:1984 console.trace
hit @ VM6:1984
VM6:1986 ~coupang.com,~coupangcdn.com#%#//scriptlet("set-constant", "PartnersCoupang", "undefined") trace end
发布评论
评论（2）
即使这有一个公认的答案，它仍然没有回答为什么Adguard必须添加这些脚本。
这是为了防止愤世嫉俗的“受众群体API”，该命名为“受保护的受众API”，该API基本上在您的设备上进行广告拍卖。它现在是铬的一部分，但是大多数铬叉通过斑块将其清除。
Even though this has an accepted answer, it still doesn't answer why Adguard has to add those scriptlets.
It's to protect against the cynically named "Protected Audience API", which basically runs advertisement auctions on your device. It's part of Chromium now, however most Chromium forks remove it through patches.
https://developer.chrome.com/docs/privacy-sandbox/protected-audience/
啊，啊，显然这一切都来自我的adguard adblocker chrome扩展。
Ah heck, apparently this all came from my AdGuard AdBlocker Chrome extension.