You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PowerShell 7 shell integration script uses -EncodedCommand with Base64 to handle OSC 133 sequences (# Orca OSC 133 shell integration for PowerShell).
In managed corporate environments, Enterprise EDR / Antivirus solutions flag this execution pattern as suspicious under the PowerShell/Bypass.K heuristic rule due to the uninspected Base64 execution in memory.
# Orca OSC 133 shell integration for PowerShell...### Expected Behavior
Shell integration should execute cleanly without triggering EDR or Antivirus heuristic blocks.
### Suggested Fix
Avoid passing integration logic via Base64-encoded strings (-EncodedCommand) on Windows. Consider using standard script files (.ps1) or unencoded arguments to prevent false-positive alerts in enterprise environments.
Grouped under #23999, a tracking issue that sorts every antivirus/EDR report against Orca by root cause (unsigned inner binaries, relay.js script heuristics, our own PowerShell spawn shapes, certificate reputation gates, macOS endpoint agents). This issue stays open on its own merits — the tracker is for routing new reports and for not fixing the same cause five times.
Activity
nwparker commentedon Sep 30, 2026
Grouped under #23999, a tracking issue that sorts every antivirus/EDR report against Orca by root cause (unsigned inner binaries,
relay.jsscript heuristics, our own PowerShell spawn shapes, certificate reputation gates, macOS endpoint agents). This issue stays open on its own merits — the tracker is for routing new reports and for not fixing the same cause five times.