feat: log keystrokes via direct input #1079
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
williballenthin
approved these changes
Oct 13, 2025
|
should we cover IDirectInput, IDirectInput2, and IDirectInput7 as well? |
zeze-zeze
force-pushed
the
zeze/feat/DirectInput
branch
from
d0a333a to
72e1570
Compare
@zeze-zeze bump on this comment? |
|
I don't have the examples of keylogger using IDirectInput, IDirectInput2, and IDirectInput7. I'm affraid it's not proper for me to write the rule. |
|
We don't need samples to cover all features. Would you agree that the other APIs would achieve the same? |
|
Added DirectInputCreateA, DirectInputCreateW, DirectInputCreateEx from dinput.dll. |
|
thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test file: mandiant/capa-testfiles#297
reference: https://www.gironsec.com/blog/2017/07/keylogger-using-directx/