The entire bundled logic is a cursor skinner: rasterizes a packaged.cur into a canvas dataURL (:61-75) and injects a single <style> element setting `cursor: url(dataURL)` (:20-34). There is no anywhere in the four packaged scripts, no cookie, tab-content, history or page-data read, and the only outbound navigation is the install-time tabs.create and setUninstallURL to [domain withheld] (:16-25), which matches the publisher website and privacy-policy domain, so it is first-party by the disclosure rules. The bundled manifest matches the published CWS summary exactly (MV3, permissions=[storage], content_scripts all_frames at document_start, web_accessible_resources cur/*.*), which corroborates benignity; the Unit42 IoC listing, the permhash cluster's 10% malicious rate and the publisher's leave-one-out malicious count contradict it, and what those [domain withheld] landing pages actually serve is outside this ZIP - that unverifiable off-bundle surface, plus jquery. being listed in but not supplied in the extraction, is why this is likely_benign rather than false_positive. Hygiene notes only: the web_accessible_resources path `cur/*.*` is vestigial (the signed inventory contains 60 files under / and nothing under a root cur/), the listing's privacy-policy URL ([domain withheld]) differs from the publisher's ([domain withheld]), and a document_start all_frames content script with a MutationObserver on every site is more reach than a cursor skin needs.