🛡️
Safe Outreach

Is Social Post Mate (Commenter AI partner) safe on LinkedIn in 2026?

No — LinkedIn detects Social Post Mate (Commenter AI partner) (we checked it ). Social Post Mate (Commenter AI partner)'s extension ID is on LinkedIn's AED detection list (Nov 2026 snapshot), and LinkedIn's page code checks for Social Post Mate (Commenter AI partner) on every visit by requesting chrome-extension://ffebfjkgjgbpmnoogjjdgfkmiobngdnf/comment.html — a file that exists only if Social Post Mate (Commenter AI partner) is installed. Our automated scan of Social Post Mate (Commenter AI partner) 5.0.3 found code that references LinkedIn's session cookie li_at (1 matches in 1 files); whether Social Post Mate (Commenter AI partner) sends that cookie anywhere needs a manual dataflow review.

Updated · LinkedIn AED snapshot Nov 2026

ID: ffebfjkgjgbpmnoogjjdgfkmiobngdnf

Does LinkedIn detect Social Post Mate (Commenter AI partner)? What we found in its code

Detected by LinkedIn

This browser extension is actively compiled into LinkedIn's frontend detection lists. LinkedIn's scripts can detect when this is active on your browser.

LinkedIn requests: chrome-extension://ffebfjkgjgbpmnoogjjdgfkmiobngdnf/comment.html
DETECTED

What this means: detection isn't an instant ban — it's one input to LinkedIn's risk score. But it's a standing signal: it stacks with your behavior (volume, programmatic clicks) and device fingerprint, and this is just the AED list — one of LinkedIn's three detection systems (see how it works).

What our automated scan found in Social Post Mate (Commenter AI partner)'s code

We downloaded Social Post Mate (Commenter AI partner) version 5.0.3 from the Chrome Web Store on and searched its 44 code files for the patterns below. Each line shows the first place we found it.

  • Social Post Mate (Commenter AI partner)'s code references li_at — LinkedIn's session cookie, the one that keeps you logged in. 1 match in 1 file — first at background.js:323.
  • Social Post Mate (Commenter AI partner) uses the Chrome cookies API (chrome.cookies), which reads cookies of every site it has access to. 1 match in 1 file — first at background.js:281.
  • Social Post Mate (Commenter AI partner) creates synthetic clicks or keystrokes (dispatchEvent / MouseEvent) — LinkedIn can tell these from real input (isTrusted=false). 5 matches in 1 file — first at sites/commenterAI.popover.js:3121.
  • Social Post Mate (Commenter AI partner) makes its own network requests (fetch / XHR / WebSocket). 40 matches in 12 files — first at background.js:7.
  • Social Post Mate (Commenter AI partner)'s code mentions linkedin.com. 14 matches in 5 files — first at background.js:100.
Permissions Social Post Mate (Commenter AI partner) asks for
storageclipboardWriteunlimitedStoragecookieswebNavigationhttps://app.commenter.ai/*https://*.linkedin.com/*https://*.unipile.com/*

What this scan is — and isn't. It is an automated static search of the shipped package, not a full teardown: a match means the pattern is in the code, not that Social Post Mate (Commenter AI partner) misuses it, and no match doesn't prove absence (minified or runtime-built code can hide it). We haven't traced where Social Post Mate (Commenter AI partner) sends data. How we test

How LinkedIn checks for Social Post Mate (Commenter AI partner): the AED probe

That verdict isn't a guess. This is what LinkedIn's own page code does on every visit — simplified from its production bundle, which the BrowserGate investigation reverse-engineered line by line:

// LinkedIn's page bundle — simplified from BrowserGate's teardown
const hits = [];
for (const { id, file } of AED_LIST) // 4,934 ids incl. this one
try { await fetch("chrome-extension://" + id + "/" + file); hits.push(id); }
catch {} // not installed → silently swallowed
fireTrackingPayload("AedEvent", { browserExtensionIds: hits }); // → POST /li/track
// this extension is probed at:
// chrome-extension://ffebfjkgjgbpmnoogjjdgfkmiobngdnf/comment.html
On LinkedIn’s AED list
Yes
1 of 4,934 · snapshot Nov 2026
URL LinkedIn requests
chrome-extension://ffebfjkgjgbpmnoogjjdgfkmiobngdnf/comment.html
the extension's ID + a file bundled inside it
Store status
Live on the Web Store
Source
LinkedIn bundle
ℹVerify it yourself: on linkedin.com open DevTools → Sources and search the page bundle for ffebfjkgjgbp… or AedEvent; or Network → filter li/track to watch the verdict ship. The scan runs even in Incognito. Below — the full code-level teardown.
Social Post Mate (Commenter AI partner) — marketed on the Chrome Web Store, detected by LinkedIn
Vendor's own Chrome Web Store screenshot — this extension is on LinkedIn's detection list.

How LinkedIn fingerprints your browser while you use Social Post Mate (Commenter AI partner)

Even after a cookie is copied out, LinkedIn keeps one more receipt on every request that follows — a 48-point snapshot of the exact machine making it. Faking it convincingly means reproducing that machine's quirks, not just editing a string.

Click any signal above for what it means. These are illustrative values — this demo never reads your actual device.

Your 48-point fingerprint — RSA-encrypted, attached to every API call in this session, not just login

This extension runs inside your real browser, so its requests always carry your real fingerprint — that isn't something it controls, it's simply where its code executes.

Verified against LinkedIn source-code, Nov 2026 snapshot.Read full study

Similar LinkedIn tools we checked

Same architecture and risk as Social Post Mate (Commenter AI partner) — each with its own code audit.

All extension checks