Skip to content

Expand CRED-6 to cover credential exposure on other site server shares#51

Merged
Mayyhem merged 2 commits intosubat0mik:mainfrom
chryzsh:cred6-site-server-shares
Mar 30, 2026
Merged

Expand CRED-6 to cover credential exposure on other site server shares#51
Mayyhem merged 2 commits intosubat0mik:mainfrom
chryzsh:cred6-site-server-shares

Conversation

@chryzsh
Copy link
Copy Markdown
Contributor

@chryzsh chryzsh commented Mar 22, 2026

After a brief discussion with @Mayyhem over DMs on the Bloodhound slack, I told him about how I've found SCCM Administrator creds on the SCCM share. I'm therefore proposing broadening the scope of CRED-6 beyond SCCMContentLib$ to include other shares commonly found on SCCM site servers (temp directories, script staging folders, admin shares) that frequently contain hardcoded credentials. Added T1552.001 TTP for unsecured credentials in files.

Let me know what you think.

Broaden scope beyond SCCMContentLib$ to include other shares commonly
found on SCCM site servers (temp directories, script staging folders,
admin shares) that frequently contain hardcoded credentials. Added
T1552.001 TTP for unsecured credentials in files.
@Mayyhem
Copy link
Copy Markdown
Collaborator

Mayyhem commented Mar 24, 2026

Thanks for the PR @chryzsh ! Could you please add operational tradecraft (e.g., tooling, specific commands, etc.) to support the techniques you're suggesting we add, as well as corresponding defensive techniques?

- Add smbclient.py example for enumerating non-default shares
- Add real-life examples of credential exposure in non-standard shares
- Cross-reference RECON-2 for identifying standard vs non-default SCCM shares
@chryzsh
Copy link
Copy Markdown
Contributor Author

chryzsh commented Mar 24, 2026

I added an operational tradecraft example, rewrote language to provide some examples and make it clearer. Defense here would mainly be to not expose non-default shares and to not put creds in files. As neither are SCCM specific, I'm not sure if they warrant a new defensive technique in this repo. I'm happy to add a suggestion for that if you do want it though.

@Mayyhem Mayyhem merged commit 3965e88 into subat0mik:main Mar 30, 2026
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.

2 participants