{"id":7855,"date":"2021-10-09T06:44:16","date_gmt":"2021-10-09T06:44:16","guid":{"rendered":"https:\/\/www.hexacorn.com\/blog\/?p=7855"},"modified":"2021-10-09T06:46:56","modified_gmt":"2021-10-09T06:46:56","slug":"trololololobin-and-other-lolololocoasters","status":"publish","type":"post","link":"https:\/\/www.hexacorn.com\/blog\/2021\/10\/09\/trololololobin-and-other-lolololocoasters\/","title":{"rendered":"Trololololobin and other lolololocoasters"},"content":{"rendered":"\n

In my older tweet<\/a> I gave an example of a surgical way to inject process into a chain of executed programs and launch them at a predetermined position in a great-great-great\u2026.grand-parent-child relationship by using the start <\/em>command:<\/p>\n\n\n\n

start \/b \"\" start \/b \"\" start \/b \"\" start \/b \"\" start \/b \"\" start \/b notepad.exe<\/pre>\n\n\n\n
\"\"<\/a><\/figure><\/div>\n\n\n\n
Many Lolbins focus on loading DLLs, downloading files, etc. I was wondering if there is a class of Lolbins that could be used to generate this kinda process tree. The idea being that if we can find it, we can create more ‘signed executable’ chains and potentially disrupt parent-child relationship-based EDR detections.<\/p>\n\n\n\n
After combing through my file collection I found one candidate and I suspect there will be others.<\/p>\n\n\n\n
The Toshiba’s signed tinstall.exe<\/em> is an executable that is a part of many installs from this company. When launched, it spawns a child process which is a next step of the installation. The peculiar way it is doing it is providing us the feature I described above. When launched, it takes its own file name, and appends ‘wb’ to it, and then launches a program with that newly created name. Under normal circumstances, the name of the spawned process will be tinstallwb.exe<\/em>. <\/p>\n\n\n\n
By placing a number of copies of tinstall.exe<\/em> in files named .exe<\/em>, wb.exe<\/em>, wbwb.exe<\/em>, wbwbwb.exe<\/em>, etc. we can build a chain of process spawned from signed executables with the wbwbwbwbwbwbwb.exe<\/em> being the final ‘payload’:<\/p>\n\n\n\n
\"\"<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"
In my older tweet I gave an example of a surgical way to inject process into a chain of executed programs and launch them at a predetermined position in a great-great-great\u2026.grand-parent-child relationship by using the start command: start \/b “” … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[56,64],"tags":[],"_links":{"self":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/7855"}],"collection":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/comments?post=7855"}],"version-history":[{"count":3,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/7855\/revisions"}],"predecessor-version":[{"id":7860,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/posts\/7855\/revisions\/7860"}],"wp:attachment":[{"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/media?parent=7855"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/categories?post=7855"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hexacorn.com\/blog\/wp-json\/wp\/v2\/tags?post=7855"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}