"2FA security detected, this Sales Navigator account can't use this Phantom" means PhantomBuster encountered an enterprise security challenge mid-run - SSO, MFA, or a corporate device policy - and exited rather than continuing in an unknown state. This is not caused by your personal 2FA setting. PhantomBuster can't bypass enterprise security prompts; the fix requires an account-level change.
What this error means
When your Phantom runs a Sales Navigator session, it may hit a security challenge enforced by your company's identity provider. When that happens, the Phantom detects it and exits immediately. You'll see this in the logs:
"2FA security detected, this Sales Navigator account can't use this Phantom."
What's actually causing this, and what's not
This error is not caused by your personal 2FA setting. Turning off 2FA on your LinkedIn account will not fix it.
The real cause is an enterprise IT security policy on the LinkedIn or Sales Navigator account. Three scenarios typically trigger it:
- Enforced SSO (via Entra ID, Okta, or a similar identity provider): your company requires login through a corporate portal PhantomBuster can't navigate.
- MFA enforced at the identity provider level: a second-factor prompt injected by your IT environment, not by LinkedIn itself.
- Corporate-managed device policies: security controls that add login challenges mid-session.
In all three cases, the Phantom's session hits a prompt it can't click through, and exits.
How to fix it
PhantomBuster can't bypass enterprise security prompts. The fix requires one of two account-level changes:
Option 1: Ask IT to carve an exception for this LinkedIn account
Have your IT team exclude the LinkedIn account used by PhantomBuster from the SSO or MFA policy. This lets the Phantom maintain its session without hitting a security challenge mid-run.
Option 2: Use a different LinkedIn account
Switch to a LinkedIn account not subject to the enterprise policy — a personal account with Sales Navigator access, or a dedicated automation account IT has excluded from corporate SSO.
→ See Two-factor Authentication (2FA) and PhantomBuster: What you Need to Know for general 2FA context.
Frequently asked questions
Why can't PhantomBuster click through the security prompt?
Enterprise security challenges (SSO portals, MFA prompts) are specifically designed to block automated access and require a human to complete them. PhantomBuster can't interact with them.
My personal 2FA is already off. Why am I still seeing this?
The error is triggered by IT-level policies on the account, not your personal LinkedIn 2FA setting. An SSO or MFA policy enforced by your company's IT team will still cause this error even when personal 2FA is disabled.
What if my whole company uses SSO for LinkedIn?
The only option is a LinkedIn account excluded from the SSO policy, typically a personal account or a dedicated automation account IT has whitelisted. If that's not possible, no Phantom can run on an account fully locked behind enterprise SSO.
Is this a PhantomBuster bug?
No. The Phantom detects the security challenge and exits cleanly rather than getting stuck. The root cause is the IT policy on the LinkedIn account.
Does this affect all Sales Navigator Phantoms?
Any Phantom using a Sales Navigator session can be affected if the account is subject to enterprise security policies.