Is Todobook safe on LinkedIn in 2026?

Not right now — LinkedIn dropped Todobook from its detection list (we checked it ). Todobook was on LinkedIn's AED list in the Feb 2026 capture but isn't on the current one (Nov 2026 snapshot) — LinkedIn rotates the list, so Todobook can be added back at any time, and page scans and device fingerprinting still apply.

Updated · LinkedIn AED snapshot Nov 2026

ID: ihbejplhkeifejcpijadinaicidddbde

Does LinkedIn detect Todobook? What we found in its code

Everything we confirmed in Todobook's code, grouped by what it means for your account. Red = strongest detection / risk signals, amber = notable, grey = neutral or local-only.

Was on LinkedIn's list — not on the current one

This extension's ID was in LinkedIn's AED detection list in the Feb 2026 capture, but LinkedIn removed it by the Nov 2026 snapshot. LinkedIn rotates this list — between those two captures it dropped 2,544 extensions and added 1,325 — so a dropped ID can come back.

Not a clean bill of health. AED is only one of LinkedIn's detection systems: page scans for injected code and device fingerprinting need no list at all. See how it works →

We read Todobook's codeMEDIUM RISK

Runs locally — session stays in your browser · not on the AED list (still detectable)

Todobook's detection surface

Signals LinkedIn's own page scripts can pick up directly on every visit — the extension probe (AED), code injected into the page (Spectroscopy), fake (isTrusted:false) clicks, blocked/missing telemetry, and cloud remote-control. Each adds points to its risk score.

AED-listed · probe chrome-extension://ihbejplhkeifejcpijadinaicidddbde/css/hn.cssSynthetic clicks (isTrusted:false)

What Todobook does with your session

How the tool touches your LinkedIn login. If it uploads your session cookie to the vendor's cloud, the vendor can act as you from another IP — LinkedIn's loudest parallel-access tell. Reading the cookie locally (csrf/Voyager) is far less risky.

no session access

Where Todobook sends your data

Every outbound destination found in the code — your session / scraped data, plus analytics, CRM pushes and CAPTCHA-solving services. LinkedIn can't see these, but it's where your data actually ends up.

—ssl.google-analytics.com

Permissions Todobook requests

Chrome permissions the extension was granted on install. The highlighted ones are the powerful kind — cookies (read your session), webRequest/declarativeNetRequest (watch & rewrite traffic, incl. blocking LinkedIn's telemetry), scripting/tabs (inject into pages).

tabsstorageunlimitedStoragedeclarativeContent

Evidence in Todobook's code (signal counts)

How many times each tell-tale pattern appears in the extension's code — the raw proof behind everything above (e.g. li_at = session-cookie reads, voyager/csrf = LinkedIn API calls, synthetic_event = fake clicks, recaptcha = challenge handling).

synthetic_event ×2programmatic_click ×1remote_script ×3
0 capabilities mapped · 9 settings · MV2
Todobook — 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 does Todobook hook into your LinkedIn tab?

There's no 'authorize with LinkedIn' step anywhere. Simplified from its manifest — here's what actually happens between install and your first page load.

linkedin.com

Permissions granted on install:

tabsstorageunlimitedStoragedeclarativeContent

4 permissions requested — no LinkedIn login involved

Step 1 of 3 — Install

Does Todobook upload your LinkedIn session?

Where your session and data actually go, reconstructed from Todobook's code. Todobook keeps your session in your browser — it calls LinkedIn's Voyager API using your own csrf token, and only uploads results.

Voyager via csrfprofile dataresults onlyAED probeanalytics💻 Youyour LinkedIn session🧩 Todobookbrowser extensionLinkedIn☁️ Vendor backend—📊 Analyticsssl.google-analytics.com
Sessions answering to this login right now: 1🍪 no `cookies` permission requested — nothing to open

red = your session/data leaving your machine · blue/green = stays local or only results leave · dashed = LinkedIn's own detection probes

ℹLinkedIn's own "where you're logged in" page does not gain a second entry from this — a replayed cookie isn't a new login, it's the same session answering from a second place.

Does Todobook run a parallel LinkedIn session from another network?

LinkedIn doesn't need to know anything about proxies to catch this — it just needs one login cookie answering from two networks at the same time.

💻 Your deviceyour real networkLinkedIn☁️ —idle — nothing to send

Todobook keeps your session on your own device, so there's only ever one network this login answers from — there's nothing here for LinkedIn's parallel-access check to catch.

We actually measured this

We measured real exit-IP reputation for 7 vendor clouds in a dedicated study — Todobook's own infrastructure wasn't in that sample. The mechanism a session-upload creates is identical regardless: two networks, one cookie.

ℹCheck LinkedIn's own "where you're logged in" page after playing this — it stays unchanged, because to LinkedIn a replayed cookie was never a new login.

How we analysed Todobook's code

We downloaded Todobook's published Chrome Web Store package, de-minified it, and read it file by file — no live LinkedIn login. Two ways to see how:

Downloaded straight from the Chrome Web Store — the exact file your browser would install.

0/3 stages run
See the full method, step by step

How LinkedIn fingerprints your browser while you use Todobook

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 Todobook — each with its own code audit.

All extension checks

Todobook FAQ

Is Todobook safe to use on LinkedIn?

Our static code audit rates Todobook MEDIUM risk. It works through your own logged-in browser session — your cookie stays on your machine and only scraped results are uploaded — which is safer than cloud tools that take your session. It is still a Chrome extension LinkedIn can detect.

Does LinkedIn detect Todobook?

Its ID isn't on LinkedIn's AED list in our latest snapshot, but that is not the same as "undetectable": LinkedIn's detection lists grow by roughly a dozen entries a day.

Can Todobook get my LinkedIn account banned or restricted?

Detection isn't an instant ban — LinkedIn scores accounts on many cumulative signals. But Todobook stacks programmatic (isTrusted:false) clicks, and independent reviews report restrictions and permanent bans for Chrome-extension automators. Safe daily limits reduce the behavioral risk but can't offset a detectable architecture.

Does Todobook have access to my LinkedIn account?

It reads LinkedIn data through your own browser session (the Voyager API) and uploads only the results — your session token itself stays on your machine.

How does Todobook work — is it a Chrome extension or a cloud tool?

Todobook is a extension (productivity/anti-distraction overlay, no session access, no network sink) that runs inside your own Chrome browser.

What is a safer alternative to Todobook?

A standalone desktop app such as Linked Helper removes the two extension-specific detection surfaces: there is no Chrome-Store ID for LinkedIn's AED scanner to probe and nothing injected into the page for its DOM scan, and your session never leaves your machine. No tool is unbannable, but the surface it exposes is far smaller.