Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

this issue is back. See below #60

Open
oasec1 opened this issue Oct 10, 2023 · 4 comments
Open

this issue is back. See below #60

oasec1 opened this issue Oct 10, 2023 · 4 comments

Comments

@oasec1
Copy link

oasec1 commented Oct 10, 2023

image
@Rurik
Copy link
Owner

Rurik commented Oct 12, 2023

Is this a case where procmon64 is being overwritten by malware? Sorry. I searched but couldn't find old context.

@oasec1
Copy link
Author

oasec1 commented Oct 21, 2023 •
edited
Loading

No I haven't seen ransomware at all for testing so I dont believe that its the case. Also back is the missing output into the text
file

@oasec1 oasec1 closed this as completed Oct 21, 2023
@Rurik
Copy link
Owner

Rurik commented Oct 22, 2023

OK, if this continues provide -d debug logs. The procmon is unusual and could be a case of procmon on 64-bit dropping a secondary 64-bit executable and Noriben having trouble there. But, that should be managed by procmon. That may need to be investigated on my end.

Opening issue for me to do that research on my backlog.

@Rurik Rurik reopened this Oct 22, 2023
@oasec1
Copy link
Author

oasec1 commented Oct 22, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Rurik @oasec1