Is myfaveTT - download all TikToks you've loved safe?

Low risk

myfaveTT is low risk. It gives the remote ui.myfavett.com frame and its own sidebar permission to access local network addresses, which the browser normally restricts. This depends on that vendor-hosted page.

Zeeingsoftv1.12.89Extension ID gmajiifkcmjkehmngbopoobeplhoegadChrome Web Store
17Risk
Who publishes it

Zeeingsoft - 2 other listings from the same operator, none carrying a finding

Publisher
Zeeingsoft

Same store account

2 other listings published from this account, 110k+ users between them, none of them carrying a finding.

AI-assisted analysis.

myfaveTT findings

Extension lets a vendor-hosted page reach devices on your local network

LowunwantedCWE-829Dynamic sandbox

It gives the remote ui.myfavett.com frame and its own sidebar permission to access local network addresses, which the browser normally restricts.

What actually happens

You did this

You open https://www.tiktok.com/ (home, Explore, or For You tab).

The myfaveTT content script (c.js) is configured to run automatically on any of these three paths.

The extension did this

The extension's sidebar iframe and a nested remote iframe get allow="local-network-access *", opting both out of Chrome's default block on private-network requests.

The grant targets the extension's own wrapper page and one specific remote iframe (ui.myfavett.com); a second remote iframe on the same page (resync.myfavett.com) is not given the same permission.

The code that does this

The sidebar and nested iframe gain local-network-access between v1.12.51 and v1.12.63.

Readable version

c.js — sidebar iframe creation (annotated)

// c.js — runs automatically on https://www.tiktok.com/, /explore, /foryouif (location.hostname === "www.tiktok.com" && self === top &&    ["/", "/explore", "/foryou"].includes(location.pathname)) {  // ...loads s.js as a page-world module (unrelated to this claim)...  const container = document.createElement("aside");  container.id = "myfaveTT-container";  const sidebar = document.createElement("iframe");  sidebar.src = chrome.runtime.getURL("rl.html");  sidebar.name = "sidebar";  sidebar.id = "myfaveTT";  // NEW in v1.12.63 — was not present in v1.12.51:  sidebar.allow = "local-network-access *";  container.appendChild(sidebar);  document.body.classList.add("pushed-by-myfaveTT");  document.body.prepend(container);}

r.js — nested remote iframe creation (annotated)

// r.js — runs inside rl.html, the sidebar iframe's own documentconst TIKTOK_ORIGIN = "https://www.tiktok.com";const UI_ORIGIN = "https://ui.myfavett.com";const uiFrame = document.createElement("iframe");uiFrame.src = UI_ORIGIN;uiFrame.id = "ui";// NEW in v1.12.63 — was not present in v1.12.51:uiFrame.allow = "local-network-access *";document.body.appendChild(uiFrame);const RESYNC_ORIGIN = "https://resync.myfavett.com";const resyncFrame = document.createElement("iframe");resyncFrame.src = RESYNC_ORIGIN;resyncFrame.id = "resync";// resyncFrame.allow is never set — this sibling frame does NOT get the grant.document.body.appendChild(resyncFrame);// ...postMessage relay between the three frames (unrelated to this claim)...

Page DOM modified

Both the sidebar's own iframe and the nested ui.myfavett.com iframe gained allow="local-network-access *" between v1.12.51 and v1.12.63. The sibling resync.myfavett.com iframe on the same page was not given the attribute in either version.

Target
the myfaveTT sidebar iframe (#myfaveTT) and its nested remote iframe (#ui, src=https://ui.myfavett.com) on tiktok.com
Before
<iframe src="chrome-extension://gmajiifkcmjkehmngbopoobeplhoegad/rl.html" name="sidebar" id="myfaveTT"></iframe><!-- inside rl.html --><iframe src="https://ui.myfavett.com" id="ui"></iframe><iframe src="https://resync.myfavett.com" id="resync"></iframe>
After the extension changed it
<iframe src="chrome-extension://gmajiifkcmjkehmngbopoobeplhoegad/rl.html" name="sidebar" id="myfaveTT" allow="local-network-access *"></iframe><!-- inside rl.html --><iframe src="https://ui.myfavett.com" id="ui" allow="local-network-access *"></iframe><iframe src="https://resync.myfavett.com" id="resync"></iframe> <!-- sibling frame: still no allow attribute -->

Remote origins loaded inside the sidebar, and which one received the permission grant

    • ui.myfavett.com

    Remote UI loaded in the sidebar. Since v1.12.63 it's granted local-network-access, letting it attempt private/loopback requests Chrome normally blocks. Behavior isn't observable.

    • resync.myfavett.com

    A second remote frame loaded in the same sidebar. Not granted the local-network-access permission, so it remains subject to Chrome's default block on private-network requests.

What Local Network Access is, and what we didn't test

Chrome's Local Network Access policy blocks embedded web content from reaching private IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and localhost — a defense against pages using a visitor's browser to reach devices on their home or office network. Setting allow="local-network-access *" on an iframe opts that frame out of the block. We did not observe ui.myfavett.com attempt to reach any private-network address during our test session, and its server-side behavior can change at any time without a new extension release. This claim documents the capability being granted, not observed scanning or exploitation.

myfaveTT version history

  1. 1.12.51

    Mar 4, 2026

  2. +7 more

  3. 1.12.84

    Nov 14, 2026

  4. 1.12.87

    Nov 20, 2026

  5. 1.12.89

    Nov 21, 2026

Chrome Web Store listing

Versions
1.12.89 latest of 11 seen since March 4, 2026
Store rating
4.8 from 707 ratings
Last updated
November 14, 2026
Size
39.07 KiB
Privacy policy
zeeingsoft.com
Updated November 20, 2026