> For the complete documentation index, see [llms.txt](https://docs.bdurham.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bdurham.dev/old-projects/tcm-secs-windows-wifi-extractor.md).

# TCM-Sec's Windows WiFi Extractor

{% embed url="<https://github.com/hmaverickadams/Windows-WiFi-Extractor>" %}

## About&#x20;

* Contributed to TCM Security's development of their Windows WiFi Extractor tool.
* The program is designed to dump WiFi SSIDs and plaintext keys from Windows hosts utilizing the built-in netsh utility.
* Forked the original repo and converted the code to run in-memory only, as the original code created files (and therefore traces) on the victim computer.
* As a result: removed reliance on hard-coded integer accessors to parsed XML data and moved to a human-readable JSON format.

## Postmortem

* When you get excited to contribute to a cybersec superstar's repo because you see an obvious code optimization, don't forget to erase hard-coded sensitive information from testing prior to making a pull request... Whoops! 😬


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bdurham.dev/old-projects/tcm-secs-windows-wifi-extractor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
