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

Improve recognizing when to rebuild import table from scratch #89

Closed
hasherezade opened this issue Sep 3, 2021 · 1 comment
Closed

Comments

@hasherezade
Copy link
Owner

Example:

  • Project1.vmp.exe
    This crackme is packed with VMProtect, and a new Import Table is loaded during the execution.

PE-sieve run with option /imp 1 (autodetect) reports that the import table is fine, and does not need the reconstruction:

imp_ok

However, seeing the report with imports (400000.Project1.vmp.exe.imports.txt) we can see that there are additional IATs. Such condition should be a trigger to rebuild the whole table.

@hasherezade
Copy link
Owner Author

Result - if run in /imp 1 mode, detection of additional IATs cause Import Table recreation :

imp_result

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

1 participant