Skip to content

[codex] Harden privacy and stealth surfaces#1

Merged
G-man3207 merged 1 commit into
mainfrom
codex/privacy-stealth-hardening
Apr 18, 2026
Merged

[codex] Harden privacy and stealth surfaces#1
G-man3207 merged 1 commit into
mainfrom
codex/privacy-stealth-hardening

Conversation

@G-man3207
Copy link
Copy Markdown
Owner

Summary

Hardens Static's anti-fingerprinting behavior across several detector-visible surfaces:

  • Removes own-property fingerprints from fake fetch and XHR decoy responses by storing fake state behind prototype accessors.
  • Keeps passive non-persona element probes native-like: page-visible URLs remain coherent while resources fail locally with error events.
  • Lets sendBeacon(chrome-extension://...) use Chrome's native HTTP(S)-only validation after logging the probe.
  • Requires stronger repeated evidence before Noise claims unknown extension-shaped IDs, while keeping known plausible IDs eligible after the existing lower threshold.
  • Adds per-origin persona rotation phase jitter so rotations do not align globally.
  • Makes shareable research exports hash origin and extension-ID labels with a per-export salt that is not retained.

Validation

  • npm run check
    • strict ESLint
    • static validation
    • 30 Playwright-backed extension tests under Xvfb

Notes

The raw export remains full fidelity for private archival. The shareable export is intentionally less useful for cross-user joining because privacy is the stricter default.

@G-man3207 G-man3207 marked this pull request as ready for review April 18, 2026 17:44
@G-man3207 G-man3207 merged commit d9b4575 into main Apr 18, 2026
2 checks passed
@G-man3207 G-man3207 deleted the codex/privacy-stealth-hardening branch April 18, 2026 17:44
G-man3207 added a commit that referenced this pull request Apr 18, 2026
[codex] Harden privacy and stealth surfaces
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant