Skip to content

[Bug]: [AV False Positive] PowerShell OSC 133 integration triggers 'PowerShell/Bypass.K' EDR flag #16629

Open

Description

@JHONR2

Operating system

Windows

Orca version

No response

Details

Description

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.

Environment

  • OS: Windows 11 / Windows 10
  • PowerShell Version: PowerShell 7.x (pwsh.exe)
  • Detection Type: Antivirus / EDR Alert (PowerShell/Bypass.K)

Decoded Script Trigger

# 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.

Activity

  1. added theissue type on Aug 26, 2026
  2. nwparker commented on Sep 30, 2026

    @nwparker
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions