-
Notifications
You must be signed in to change notification settings - Fork 563
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
Multiple issues extracting macro. #623
Comments
I think this is a duplicate of #455 and if so, it has been fixed in the latest dev version. Will check and update this. |
OK - thanks for the fast response. Cheers, |
Unfortunately the sample cannot be downloaded from hybrid-analysis.com, and I cannot find it elsewhere. Could you please make it downloadable on HA, or else upload it here in a password-protected zip? Thanks. |
Hello, Apologies for that - I uploaded it to HA and had done so deliberately in order to create this issue - it should allow you to download the sample if you have a public account. In terms of how it works, it does produce an error but also produces some valid output:
This might be because it looks like that particular sample has been messed around with by AV vendors removing macro code. I think the warning message is probably OK, but perhaps the error message should be debug/warning? In any case, the original ticket can now be closed. Cheers, |
I do have a HA account, but the sample is tagged as not downloadable. |
Affected tool:
olevba
Describe the bug
OleVBA fails to extract embedded macro in document due to multiple errors.
File/Malware sample to reproduce the bug
https://hybrid-analysis.com/sample/bbe0ecfae4eea9b798676c8a898b034bfbc63c712e83dbc0338dc793c7490fe9
How To Reproduce the bug
λ olevba bbe0ecfae4eea9b798676c8a898b034bfbc63c712e83dbc0338dc793c7490fe9.MLWR
Expected behavior
It should extract the macros, but it fails for a number of reasons - the errors are a mix of:
Resolving part 2) is trivial but I'm unsure on part 1.
Console output / Screenshots
Version information:
Additional context
Nope!
The text was updated successfully, but these errors were encountered: