Fishing (phishing?) around

What the Monotype rep did next is kind of what a malicious hacker does when they’re trying to get someone from your company to click on a link that’ll install malware on your computer. Over the next couple of weeks, the rep messaged a dozen or so more people from different parts of the business, hoping to hook just one person who would reply to the scary message they were sending.

Now I’d already emailed my design, brand, and digital team colleagues to tell them about this mass-messaging campaign and our plan of action for it, but the Monotype rep expanded their campaign to include people from our procurement team, who I hadn’t thought to forewarn.

So not long after, I received a message from one of my procurement team colleagues who’d been forwarded that LinkedIn message from their senior manager with an instruction to deal with this. I explained to my colleague that, as far as I could tell, this Monotype campaign was similar to the domain name scams the procurement team is already familiar with. So please sit tight till our digital team colleagues have completed their audit and then we’ll figure out which one person should start the conversation with Monotype.

But, like any successful phishing campaign, the Monotype rep’s LinkedIn messages eventually reached someone who did respond. This was another person in the procurement team and, just to be completely clear, I don’t blame them for responding. They were just doing their job of protecting our business from potential copyright liability.

Being forced to deal with the issue

Since I’d handed this over to the digital team, I hadn’t kept track of how things were progressing. I was brought back into the discussion when our brand manager included me in an email thread between her and the procurement person who’d responded to Monotype.

I quickly brought this second procurement person up to speed with our earlier plan of action and then I looped in the digital team again. Turns out the digital team had completed their audit, found that we were in compliance, but had gotten busy with other work so no one had responded to Monotype. *sigh*