<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://atakinjector.github.io/</id><title>Atakilti Archive</title><subtitle>Personal research, experiments and notes</subtitle> <updated>2026-04-13T21:37:58+02:00</updated> <author> <name>Atakilti Tigabu</name> <uri>https://atakinjector.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://atakinjector.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://atakinjector.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Atakilti Tigabu </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>Finding Module Address through PEB</title><link href="https://atakinjector.github.io/posts/peb-module-enumeration/" rel="alternate" type="text/html" title="Finding Module Address through PEB" /><published>2026-04-07T18:00:00+02:00</published> <updated>2026-04-07T18:00:00+02:00</updated> <id>https://atakinjector.github.io/posts/peb-module-enumeration/</id> <content type="text/html" src="https://atakinjector.github.io/posts/peb-module-enumeration/" /> <author> <name>Atakilti Tigabu</name> </author> <category term="malware" /> <category term="windows-internals" /> <summary>Introduction Generally, programs resolve specific module addresses (such as kernel32.dll) by calling windows api like GetModuleHandle() or through native api like NtQuerySystemInformation. However, this leaves alot of traces and can be easily detected by EDRs or by simplying analysing the Import Address Table (IAT) in the PE strucuture of the binary program. To stay stealthy, malware devs resol...</summary> </entry> </feed>
