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

scan: --err-first-hit exits before showing matched output #623

Closed
tstromberg opened this issue Nov 14, 2024 · 1 comment Β· Fixed by #624
Closed

scan: --err-first-hit exits before showing matched output #623

tstromberg opened this issue Nov 14, 2024 · 1 comment Β· Fixed by #624
Assignees

Comments

@tstromberg
Copy link
Collaborator

Possibly related to #617 - but also possibly before that. /cc @egibs

 go run ./cmd/mal --err-first-hit scan /usr
πŸ”Ž Scanning "/usr"
πŸ‘‹ scan: "/usr/bin/busybox": matched requested condition

What I would have expected to before the exit is:

β”œβ”€ 😈 /usr/bin/busybox
β”‚     β€’ anti-behavior/anti_debugger β€” multiple suspicious methods to detect a debugger:
β”‚     /proc/%u/exe, /proc/self/exe, /sys/devices/system/cpu, LD_DEBUG, LD_PROFILE
β”‚     β€’ discover/network/interface_list β€” list network interfaces, avoids debugging:
β”‚     LD_DEBUG, LD_PROFILE, gethostbyname, getifaddrs
β”‚     β€’ hw/dev/ubi β€” access raw unsorted block images (UBI): /dev/ubi%u
@egibs
Copy link
Member

egibs commented Nov 14, 2024

Good catch. Shouldn't be too hard to render before running cancel(). I'll look into this πŸ‘πŸ»

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 a pull request may close this issue.

2 participants