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.

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

Using the flare-floss analysis module results in terminated by signal SIGKILL (Forced quit) #2440

Closed
seanthegeek opened this issue Dec 23, 2024 · 10 comments

Comments

@seanthegeek
Copy link
Contributor

'sudo -u cape poetry run python…' terminated by signal SIGKILL (Forced quit)

@doomedraven
Copy link
Collaborator

ouch wow, could you share hash to try to reproduce it?

@seanthegeek
Copy link
Contributor Author

@doomedraven
Copy link
Collaborator

i was able to reproduce it, i guess we can add handling but it would be good to report that to flare so they can investigate it properly

@doomedraven
Copy link
Collaborator

ok i even have added sigterm handling, it still kills console, so i can't do much here, sadly is out of cape control, i don't want to intercept all linux signals

@doomedraven
Copy link
Collaborator

i have tried with sigint and sigterm handling, still kills the console

@doomedraven
Copy link
Collaborator

so far it only happens to dotnet file 8961fee08f2fd802c671b00dd845f7dfad9748c317e57aa675774a034319d89e if deobfusacte strings enabled, if deobfuscation is not enabled it works fine

@seanthegeek
Copy link
Contributor Author

Where did that second hash come from? I can't find it on VT.

@seanthegeek
Copy link
Contributor Author

Reported. mandiant/flare-floss#1087

@doomedraven
Copy link
Collaborator

that file was captured by cape fro me malware execution/de4dot, i would need to check, i just disabled floss for dotnet and no crashes anymore. closing this as this is not cape issue, thanks for reporting it to floss. update cape, restart procesign and it won't happend anymore

@mr-tz
Copy link

mr-tz commented Jan 2, 2025

Thanks, reported it further upstream to vivisect. Disabling FLOSS specific extractions for .NET samples makes sense as the tool doesn't do any .NET specific handling currently.

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

No branches or pull requests

3 participants