The core issue: Windows RPC runtime doesn't verify whether the server a high-privileged client connects to is legitimate. If a target RPC server is unavailable, an attacker with SeImpersonatePrivilege can spin up a fake RPC server mimicking the same endpoint, wait for a SYSTEM-level client to connect, then call RpcImpersonateClient to escalate privileges.

Five confirmed escalation paths:

- gpupdate /force → SYSTEM (coerces Group Policy service)

- Microsoft Edge launch → Administrator (no coercion needed)

- WDI background service → SYSTEM (fires every 5–15 min automatically)

- ipconfig + disabled DHCP → Administrator

- w32tm.exe → Administrator via non-existent named pipe

Microsoft assessed this as moderate severity, issued no CVE, and has no patch planned — justification being that SeImpersonatePrivilege is a prerequisite.

Questions for the community:

1. Are you monitoring for RPC_S_SERVER_UNAVAILABLE (Event ID 1 via ETW) in your environment?

2. Any Sigma/Defender rules already written for this?

3. Do you agree with Microsoft's severity assessment given how common SeImpersonatePrivilege is on IIS/SQL servers?

Kaspersky's full write-up + PoC: https://securelist.com/phantomrpc-rpc-vulnerability/119428/

I wrote a full technical breakdown of the CISA/Nightwing GitHub credential leak that dropped last week. Sharing here because the coverage mostly stopped at "government agency leaked secrets" without getting into what actually failed at each layer.

What was in the repo (844 MB):

- AWS GovCloud admin keys in `Important AWS Tokens.txt`

- Browser password export: `AWS-Workspace-Firefox-Passwords.csv`

- Entra ID SAML certificates (full SSO impersonation capability)

- GitHub PATs (personal + professional)

- Kubernetes Kube-Config for CISA's Landing Zone DevSecOps cluster

- ArgoCD application files with secret-related YAML

- Terraform IaC describing internal cloud architecture

- CI/CD logs, internal documentation, service hostnames

The five defense failures I broke down:

1. Plaintext credential storage (baseline failure)

2. GitHub secret scanning deliberately disabled — this is the one that gets me. Push protection ships ON by default. Someone turned it off.

3. Shadow backup workflow — repo was structured as personal cloud storage for work assets, bypassing enterprise data controls

4. Zero internal monitoring detected this for 183 days. GitGuardian found it externally.

5. AWS GovCloud keys stayed valid for **48 hours after the repo came offline** — confirmed independently by Philippe Caturegli of Seralys

The 48h window is the underreported angle. Taking the repo down removes the exposure source. It doesn't revoke credentials already harvested. Anyone who scraped during the 183-day window still had working GovCloud admin access two days after the incident was "contained."

MITRE ATT&CK mapping: T1078, T1552.001, T1552.004, T1098, T1087, T1619, T1021, T1530, T1567.002, T1562.001

Detection rules included:

- Sigma rule for AWS key usage post-exposure (CloudTrail-based)

- gitleaks/TruffleHog scan commands

- Kubernetes API anomaly detection logic

- Honeytoken deployment strategy

Three-tier remediation plan: immediate (today), short-term (this week), strategic (30 days) — with specific commands and tooling recommendations.

Happy to discuss the detection engineering side or any of the MITRE mappings — some of them (especially T1562.001 for the secret scanning disable) are worth arguing about.

I had an idea for leaking a system prompt against a LLM powered classifying system that is constrained to give static responses. The attacker uses a prompt injection to update the response logic and signal true/false responses to attacker prompts. I haven't seen other research on this technique so I'm calling it blind boolean-based prompt injection (BBPI) unless anyone can share research that predates it. There is an accompanying GitHub link in the post if you want to experiment with it locally.

This research uncovered malware with LLM threats also shared many ideas to hunt these LLM-enabled malwares

https://blog.