Sending Spammers to Password Purgatory with Microsoft Power Automate and Cloudflare Workers KV

How best to punish spammers? I give this topic a lot of thought because I spend a lot of time sifting through the endless garbage they send me. And that’s when it dawned on me: the punishment should fit the crime – robbing me of my time – which means that I, in turn, need to rob them of their time. With the smallest possible overhead on my time, of course. So, earlier this year I created Password Purgatory with the singular goal of putting spammers through the hellscape that is attempting to satisfy really nasty password complexity criteria. And I mean really nasty criteria, like much worse than you’ve ever seen before. I open-sourced it, took a bunch of PRs, built out the API to present increasingly inane password complexity criteria then left it at that. Until now because finally, it’s alive, working and devilishly beautiful 😈

Step 1: Receive Spam

This is the easy bit – I didn’t have to do anything for this step! But let me put it into context and give you a real world sample:

Ugh. Nasty stuff, off to hell for them it is, and it all begins with filing the spam into a special folder called “Send Spammer to Password Purgatory”:

That’s the extent of work involved on a spam-by-spam basis, but let’s peel back the covers and look at what happens next.

Step 2: Trigger a Microsoft Power Automate Flow

Microsoft Power Automate (previously “Microsoft Flow”) is a really neat way of triggering a series of actions based on an event, and there’s a whole lot of connectors built in to make life super easy. Easy on us as the devs, that is, less easy on the spammers because here’s what happens as soon as I file an email in the aforementioned folder:

Using the built in connector to my Microsoft 365 email account, the presence of a new email in that folder triggers a brand new instance of a flow. Following, I’ve added the “HTTP” connector which enables me to make an outbound request:

All this request does is make a POST to an API on Password Purgatory called “create-hell”. It passes an API key because I don’t want just anyone making these requests as it will create data that will persist at Cloudflare. Speaking of which, let’s look at what happens over there.

Step 3: Call a Cloudflare Worker and Create a Record in KV

Let’s start with some history: Back in the not too distant past, Cloudflare wasn’t a host and instead would just reverse proxy requests through to origin services and do cool stuff with them along the way. This made adding HTTPS to any website easy (and free), added heaps of really neat WAF functionality and empowered us to do cool things with caching. But this was all in-transit coolness while the app logic, data and vast bulk of the codebase sat at that origin site. Cloudflare workers started to change that and suddenly we had code on the edge running in hundreds of nodes around the world, nice and close to our visitors. Did that start to make Cloudflare a “host”? Hmm… but the data itself was still on the origin service (transient caching aside). Fast forward to now and there they are multiple options to store data on Cloudflare’s edges including theirs (currently beta) R2 service, Durable Objectsthe (forthcoming) D1 SQL database and of most importance to this blogpost, Workers KV. Does this make them a host if you can now build entire apps within their environment? Maybe so, but let’s skip the titles for now and focus on the code.

All the code I’m going to refer to here is open source and available in the public Password Purgatory Logger Github repo. Very early on in the index.js file that does all the work, you’ll see a function called “createHell” which is called when the flow step above runs. That code creates a GUID then stores it in KV after which I can easily view it in the Cloudflare dashboard:

There’s no value yet, just a key and it’s returned via a JSON response in a property called “kvKey”. To read that back in the flow, I need a “Parse JSON” step with a schema I generated from a sample:

At this point I now have a unique ID in persistent storage and it’s available in the flow, which means it’s time to send the spammer an email.

Step 4: Invite the Spammer to Hell

Because it would be rude not to respond, I’d like to send the spammer back an email and invite them to my very special registration form. To do this, I’ve grabbed the “Reply to email” connector and fed the kvKey through to a hyperlink:

It’s an HTML email with the key hidden within the hyperlink tag so it doesn’t look overtly weird. Using this connector means that when the email sends, it looks precisely like I’ve lovingly crafted it myself:

With the entire flow now executed, we can view the history of each step and see how the data moves between them:

Now, we play the waiting game 😊

Step 5: Log Spammer Pain

Wasting spammer time in and of itself is good. Causing them pain by having them attempt to pass increasingly obtuse password complexity criteria is better. But the best thing – the pièce de résistance – is to log that pain and share it publicly for our collective entertainment 🤣

So, by following the link the spammer ends up here (you’re welcome to follow that link and have a play with it):

The kvKey is passed via the query string and the page invites the spammer to begin the process of becoming a partner. All they need to leave is an email address… and a password. That page then embeds 2 scripts from the Password Purgatory website, both of which you can find in the open source and public Github repository I created in the original blog post. Each attempt at creating an account sends off the password only to the original Password Purgatory API I created months ago, after which it responds with the next set of criteria. But each attempt also sends off both the criteria that was presented (none on the first go, then something increasingly bizarre on each subsequent go), the password they tried to use to satisfy the criteria and the kvKey so it can all be tied together. What that means is that the Cloudflare Workers KV entry created earlier gradually builds up as follows:

There are a couple of little conditions built into the code:

  1. If a kvKey is passed in the log request that doesn’t actually exist on Cloudflare, HTTP 404 is returned. This is to ensure randos out there don’t attempt to submit junk logs into KV.
  2. Once the first password is logged, there’s a 15 minute window within which any further passwords can be logged. The reason is twofold: firstly, I don’t want to share the spammers attempts publicly until I’m confident no more passwords can be logged just in case they add PII or something else inappropriate. Secondly, once they know the value of the kvKey a non-spammer could start submitting logs (for example, when I tweet it later on or share it via this blog post).

That’s everything needed to lure the spammer in and record their pain, now for the really fun bit 😊

Step 6: Enjoy Reveling in Spammer Pain

The very first time the spammer’s password attempt is logged, the Cloudflare Worker sends me an email to let me know I have a new spammer hooked (this capability using MailChannels only launched this year):

It was so exciting getting this email yesterday, I swear it’s the same sensation as literally getting a fish on your line! That link is one I can share to put the spammer’s pain on display for the world to see. This is achieved with another Cloudflare Workers route that simply pulls out the logs for the given kvKey and formats it neatly in an HTML response:

Ah, satisfaction 😊 I listed the amount of time the spammer burned with a goal to further refine the complexity criteria in the future to attempt to keep them “hooked” for longer. Is the requirement for a US post code in the password a bit too geographically specific, for example? Time will tell and I wholeheartedly welcome PRs to that effect the original Password Purgatory API repo.

Oh – and just to ensure traction and exposure are maximized, there’s a neatly formatted Twitter card that includes the last criteria and password used, you know, the ones that finally broke the spammer’s spirit and caused them to give up:

Summary

Clearly, I’ve taken a great deal of pleasure in messing with spammers and I hope you do too. I’ve gotta be honest – I’ve never been so excited to go through my junk mail! But I also thoroughly enjoyed putting this together with Power Automate and Workers KV, I think it’s super cool that you can pull an app together like this with a combination of browser-based config plus code and storage that runs directly in hundreds of globally distributed edge nodes around the world. I hope the spammers appreciate just how elegant this all is 🤣

Cloudflare

Source

How best to punish spammers? I give this topic a lot of thought because I spend a lot of time sifting through the endless garbage they send me. And that’s when it dawned on me: the punishment should fit the crime – robbing me of my time – which means that I, in turn, need to rob them of their time. With the smallest possible overhead on my time, of course. So, earlier this year I created Password Purgatory with the singular goal of putting spammers through the hellscape that is attempting to satisfy really nasty password complexity criteria. And I mean really nasty criteria, like much worse than you’ve ever seen before. I open-sourced it, took a bunch of PRs, built out the API to present increasingly inane password complexity criteria then left it at that. Until now because finally, it’s alive, working and devilishly beautiful 😈

Step 1: Receive Spam

This is the easy bit – I didn’t have to do anything for this step! But let me put it into context and give you a real world sample:

Ugh. Nasty stuff, off to hell for them it is, and it all begins with filing the spam into a special folder called “Send Spammer to Password Purgatory”:

That’s the extent of work involved on a spam-by-spam basis, but let’s peel back the covers and look at what happens next.

Step 2: Trigger a Microsoft Power Automate Flow

Microsoft Power Automate (previously “Microsoft Flow”) is a really neat way of triggering a series of actions based on an event, and there’s a whole lot of connectors built in to make life super easy. Easy on us as the devs, that is, less easy on the spammers because here’s what happens as soon as I file an email in the aforementioned folder:

Using the built in connector to my Microsoft 365 email account, the presence of a new email in that folder triggers a brand new instance of a flow. Following, I’ve added the “HTTP” connector which enables me to make an outbound request:

All this request does is make a POST to an API on Password Purgatory called “create-hell”. It passes an API key because I don’t want just anyone making these requests as it will create data that will persist at Cloudflare. Speaking of which, let’s look at what happens over there.

Step 3: Call a Cloudflare Worker and Create a Record in KV

Let’s start with some history: Back in the not too distant past, Cloudflare wasn’t a host and instead would just reverse proxy requests through to origin services and do cool stuff with them along the way. This made adding HTTPS to any website easy (and free), added heaps of really neat WAF functionality and empowered us to do cool things with caching. But this was all in-transit coolness while the app logic, data and vast bulk of the codebase sat at that origin site. Cloudflare workers started to change that and suddenly we had code on the edge running in hundreds of nodes around the world, nice and close to our visitors. Did that start to make Cloudflare a “host”? Hmm… but the data itself was still on the origin service (transient caching aside). Fast forward to now and there they are multiple options to store data on Cloudflare’s edges including theirs (currently beta) R2 service, Durable Objectsthe (forthcoming) D1 SQL database and of most importance to this blogpost, Workers KV. Does this make them a host if you can now build entire apps within their environment? Maybe so, but let’s skip the titles for now and focus on the code.

All the code I’m going to refer to here is open source and available in the public Password Purgatory Logger Github repo. Very early on in the index.js file that does all the work, you’ll see a function called “createHell” which is called when the flow step above runs. That code creates a GUID then stores it in KV after which I can easily view it in the Cloudflare dashboard:

There’s no value yet, just a key and it’s returned via a JSON response in a property called “kvKey”. To read that back in the flow, I need a “Parse JSON” step with a schema I generated from a sample:

At this point I now have a unique ID in persistent storage and it’s available in the flow, which means it’s time to send the spammer an email.

Step 4: Invite the Spammer to Hell

Because it would be rude not to respond, I’d like to send the spammer back an email and invite them to my very special registration form. To do this, I’ve grabbed the “Reply to email” connector and fed the kvKey through to a hyperlink:

It’s an HTML email with the key hidden within the hyperlink tag so it doesn’t look overtly weird. Using this connector means that when the email sends, it looks precisely like I’ve lovingly crafted it myself:

With the entire flow now executed, we can view the history of each step and see how the data moves between them:

Now, we play the waiting game 😊

Step 5: Log Spammer Pain

Wasting spammer time in and of itself is good. Causing them pain by having them attempt to pass increasingly obtuse password complexity criteria is better. But the best thing – the pièce de résistance – is to log that pain and share it publicly for our collective entertainment 🤣

So, by following the link the spammer ends up here (you’re welcome to follow that link and have a play with it):

The kvKey is passed via the query string and the page invites the spammer to begin the process of becoming a partner. All they need to leave is an email address… and a password. That page then embeds 2 scripts from the Password Purgatory website, both of which you can find in the open source and public Github repository I created in the original blog post. Each attempt at creating an account sends off the password only to the original Password Purgatory API I created months ago, after which it responds with the next set of criteria. But each attempt also sends off both the criteria that was presented (none on the first go, then something increasingly bizarre on each subsequent go), the password they tried to use to satisfy the criteria and the kvKey so it can all be tied together. What that means is that the Cloudflare Workers KV entry created earlier gradually builds up as follows:

There are a couple of little conditions built into the code:

  1. If a kvKey is passed in the log request that doesn’t actually exist on Cloudflare, HTTP 404 is returned. This is to ensure randos out there don’t attempt to submit junk logs into KV.
  2. Once the first password is logged, there’s a 15 minute window within which any further passwords can be logged. The reason is twofold: firstly, I don’t want to share the spammers attempts publicly until I’m confident no more passwords can be logged just in case they add PII or something else inappropriate. Secondly, once they know the value of the kvKey a non-spammer could start submitting logs (for example, when I tweet it later on or share it via this blog post).

That’s everything needed to lure the spammer in and record their pain, now for the really fun bit 😊

Step 6: Enjoy Reveling in Spammer Pain

The very first time the spammer’s password attempt is logged, the Cloudflare Worker sends me an email to let me know I have a new spammer hooked (this capability using MailChannels only launched this year):

It was so exciting getting this email yesterday, I swear it’s the same sensation as literally getting a fish on your line! That link is one I can share to put the spammer’s pain on display for the world to see. This is achieved with another Cloudflare Workers route that simply pulls out the logs for the given kvKey and formats it neatly in an HTML response:

Ah, satisfaction 😊 I listed the amount of time the spammer burned with a goal to further refine the complexity criteria in the future to attempt to keep them “hooked” for longer. Is the requirement for a US post code in the password a bit too geographically specific, for example? Time will tell and I wholeheartedly welcome PRs to that effect the original Password Purgatory API repo.

Oh – and just to ensure traction and exposure are maximized, there’s a neatly formatted Twitter card that includes the last criteria and password used, you know, the ones that finally broke the spammer’s spirit and caused them to give up:

Summary

Clearly, I’ve taken a great deal of pleasure in messing with spammers and I hope you do too. I’ve gotta be honest – I’ve never been so excited to go through my junk mail! But I also thoroughly enjoyed putting this together with Power Automate and Workers KV, I think it’s super cool that you can pull an app together like this with a combination of browser-based config plus code and storage that runs directly in hundreds of globally distributed edge nodes around the world. I hope the spammers appreciate just how elegant this all is 🤣

Cloudflare

Source

More from author

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Related posts

Advertismentspot_img

Latest posts

Apple patches double zero-day in browser and kernel – update now! – Naked Security

Apple just pushed out an emergency update for two zero-day bugs that are apparently actively being exploited. There's a remote code execution hole (RCE) dubbed...

Securing the ever-evolving hybrid work environment

Even as many business leaders debate the boundaries of remote work styles and schedules, there is little doubt that hybrid work will persist for...

Hackers Deploy Bumblebee Loader to Breach Target Networks

Threat actors associated with BazarLoader, TrickBot and IcedID malware are now increasingly deploying the loader known as Bumblebee to breach target networks and subsequently...

Want to stay up to date with the latest news?

We would love to hear from you! Please fill in your details and we will stay in touch. It's that simple!