Skip to content

Return of the Cookie Monster - #2851

Open
carlospolop wants to merge 1 commit into
masterfrom
update_Return_of_the_Cookie_Monster_bd3373b0119173e3
Open

carlospolop wants to merge 1 commit into
masterfrom
update_Return_of_the_Cookie_Monster_bd3373b0119173e3

Conversation

@carlospolop

Copy link
Copy Markdown
Collaborator

🤖 Automated Content Update

This PR was automatically generated by the HackTricks News Bot based on a technical blog post.

📝 Source Information

🎯 Content Summary

Overview

The post presents a Windows post-exploitation technique for enabling the Chrome DevTools Protocol (CDP) inside an already-running Chromium browser process, specifically chrome.exe or msedge.exe. By activating CDP in the victim's existing browser rather than launching a separate debugging instance, an operator retains access to the user's normal profile, cookies, extensions, saved data, open tabs, and authenticated sessions.

This is not a remote...

🔧 Technical Details

Activate CDP inside an authenticated browser: When Chromium refuses remote-debugging flags for the default profile, avoid starting a new browser instance. Inject into the existing chrome.exe or msedge.exe, locate its loaded browser DLL, resolve StartRemoteDebuggingServer and the required allocation and socket-factory symbols with masked signatures, place a remote stub, install a temporary window procedure, and execute the internal server-start function on the browser UI thread. This exposes a localhost CDP endpoint while retaining the user's actual profile and authenticated state.

Use the browser rather than replaying exported sessions: Encryption and device binding mainly frustrate offline cookie extraction and replay from another environment. If an attacker controls CDP in the legitimate browser, they can query Storage.getCookies or make the browser perform authenticated navigation and requ...

🤖 Agent Actions

Implemented the HackTricks update.

Changes

  • Expanded electron-cef-chromium-debugger-abuse.md with:
    • CDP-Enable-BOF and chrome-iso internals
    • Signature/PDB maintenance workflow
    • CDP Toolkit commands and WebUI automation
    • ABE/device-bound session implications
    • Browser takeover and authenticated proxying
    • Sysmon Event 8/10 detection, including the complete 0x143a mask
  • Added navigation from Windows credential-stealing documentation.
  • Added numbered citations for primary research, tool repositories, Microsoft documentation, and the supplied SpecterOps post.

Validation

  • git diff --check passed.
  • Internal reference and citation checks passed.
  • Confirmed no forbidden sources were added.
  • mdbook was unavailable in the environment.

This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.

@carlospolop

Copy link
Copy Markdown
Collaborator Author

🔗 Additional Context

Original Blog Post: https://specterops.io/blog/2026/08/13/chrome-devtools-protocol-cookie-theft

Content Categories: Based on the analysis, this content was categorized under "Windows Hardening > Stealing Windows Credentials > Browser Session and Cookie Theft via Chrome DevTools Protocol".

Repository Maintenance:

  • MD Files Formatting: 1029 files processed

Review Notes:

  • This content was automatically processed and may require human review for accuracy
  • Check that the placement within the repository structure is appropriate
  • Verify that all technical details are correct and up-to-date
  • All .md files have been checked for proper formatting (headers, includes, etc.)

Bot Version: HackTricks News Bot v1.0

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