Skip to content

Initial support for WMI spoofery - #161

Merged
kevoreilly merged 1 commit into
kevoreilly:capemonfrom
doomedraven:opt/wmi-spoofing-only
Aug 17, 2026
Merged

Initial support for WMI spoofery#161
kevoreilly merged 1 commit into
kevoreilly:capemonfrom
doomedraven:opt/wmi-spoofing-only

Conversation

@doomedraven

Copy link
Copy Markdown
Contributor

gemini comments review and implements from #97

@doomedraven
doomedraven force-pushed the opt/wmi-spoofing-only branch 2 times, most recently from d77a81d to a49c765 Compare August 16, 2026 11:00
@doomedraven
doomedraven force-pushed the opt/wmi-spoofing-only branch from a49c765 to c77b50e Compare August 16, 2026 11:11
@doomedraven

Copy link
Copy Markdown
Contributor Author

feel free to correct/merge/reject

@kevoreilly
kevoreilly merged commit e234325 into kevoreilly:capemon Aug 17, 2026
@doomedraven
doomedraven deleted the opt/wmi-spoofing-only branch August 17, 2026 11:31
KillerInstinct added a commit to KillerInstinct/capemon that referenced this pull request Sep 2, 2026
PR kevoreilly#116 made SpoofWmiData resolve the object's WMI __CLASS directly, so
the g_last_seen_disk_query / g_last_seen_physicalmemory flags PR kevoreilly#161
brought back from the old kevoreilly#97 patch are redundant. Worse, gating the
LogicalDisk Size and PhysicalMemory Capacity spoofs on those flags skips
spoofing whenever the class isn't reached via a SELECT on the same thread:
CreateInstanceEnum (Get-CimInstance / Get-WmiObject -Class), GetObject on
an instance, and async results delivered on the WMI sink thread.

Remove the flags and restore both ExecQuery hooks to log-before-call.
The AdapterRAM (realistic 4GB overflow value) and MaxRefreshRate spoofs
from kevoreilly#161 are correct and kept.
kevoreilly added a commit that referenced this pull request Sep 2, 2026
Drop redundant g_last_seen_* WMI query gating from PR #161
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.

3 participants