01 logo

BORIS AND NATASHA ARE BACK

HOW YOU GONNA HATE FROM OUTSIDE THE CLUB? YOU CAN'T EVEN GET IN! LEGGO!

By Dakota Denise Published a day ago • 9 min read

BORIS AND NATASHA ARE BACK: HOW YOU GONNA HATE FROM OUTSIDE THE CLUB? YOU CAN'T EVEN GET IN! LEGGO!

Pinky and the Brain have officially been retired. Apparently, these two didn't get the memo, because they're back in the Vocal Media comment section. Unfortunately for them, I have time today.

Listen.

I really thought I was done with these people.

I had already gone down the Vocal Media phishing rabbit hole, investigated the suspicious comments, examined the links, followed the redirects, checked the security reports, and written an entire damn article about it.

I was ready to get back to writing.

You know, the reason I joined Vocal Media in the first place?

But apparently, somebody had other plans.

And before I get started, I need to correct something from my previous investigation.

I initially thought the first round of suspicious comments involved ten of my stories.

NOPE.

It was TWENTY-THREE.

Twenty-three of my stories had been hit with these comments.

TWENTY-THREE!

At this point, I was beginning to wonder if somebody had mistaken my writing portfolio for a damn customer-service department.

And just when I thought the situation had settled down, here we go again.

Now, I don't know about y'all, but I think it's time for a cast change.

Pinky and the Brain are officially RETIRED.

Please welcome our newest villains:

BORIS AND NATASHA!

Because apparently, we're dealing with two people who think they're running some kind of international espionage operation.

And I have to admit, the more I investigate, the more entertaining this little situation becomes.

Not because phishing is funny. It's not.

But the audacity?

THE AUDACITY!

HOW YOU GONNA HATE FROM OUTSIDE THE CLUB?

Now, let me explain something about the Vocal Media community.

A lot of us have been here building our portfolios, publishing our work, interacting with other writers, and establishing ourselves on the platform.

You see those little blue verification check marks? You see those V+ badges?

That's our little corner of the internet.

We've got our community, our writers, our stories, our conversations, and our own little ecosystem.

And then here come Boris and Natasha, trying to sneak into the establishment wearing a fake Vocal Support name tag.

I don't know who told them they were on the guest list, but somebody needs to check that paperwork.

How you gonna hate from outside of the club? You can't even get in!

LEGGO!

And since we're talking about who belongs where, let's have a little Mean Girls moment.

You know the pink sweaters? The Wednesday dress code? The Plastics sitting together like they own the cafeteria?

Well, apparently, somebody forgot to tell Boris and Natasha that there are rules around here.

And if you've ever watched that movie, you already know the energy.

YOU CAN'T SIT WITH US!

Not at this table.

Not in this comment section.

And certainly not pretending to be somebody you're not.

The blue check marks and V+ badges are already giving community-member energy.

Boris and Natasha are giving somebody's suspicious cousin who showed up uninvited.

And I don't think the Plastics are accepting new members.

Sorry. Not sorry.

HERE WE GO AGAIN!

So, I'm minding my business, doing what I came to Vocal Media to do.

Writing.

Publishing.

Checking my stories.

Looking at my views and wondering why an article I spent three hours putting together can't get the same attention as something I wrote while sitting on the toilet.

You know, regular writer activities.

And then here comes another suspicious comment.

This time, the message reads:

"Your Vocal account has been automatically flagged as potential spam due to suspicious activity. To remove the restriction, please complete verification via the link below."

Then they provide this little invitation:

https://tr.ee/vocal-verify

And naturally, they sign off as the Vocal Support Team.

Now, who exactly authorized you to be the Vocal Support Team?

Because I certainly don't remember receiving an announcement.

Did I miss a staff meeting?

Was there an employee orientation?

Did somebody forget to send me the memo?

And why does your version of customer service involve sending writers to some mystery website to verify their accounts?

I have questions.

But instead of asking Boris and Natasha directly, I decided to do what I did the first time.

INVESTIGATE.

DETECTIVE DAKOTA IS BACK ON THE CLOCK.

If you read my previous article, I Went Down the Vocal Media Phishing Rabbit Hole (And Now Somebody Needs to Put Me on the Payroll!), you already know I didn't just look at the suspicious comments and call it a day.

I took the links and submitted them to an independent security-analysis website.

I wanted to know where they were going.

I wanted to see what happened between the original link and the final destination.

And I wanted to know whether the information I was seeing was consistent with my earlier investigation.

So, let's pull out the receipts.

INVESTIGATION NUMBER ONE: THE ORIGINAL ROUND

The first investigation involved suspicious comments on 23 of my stories.

The original URL was:

"https://tr.ee/vocal-media"

The redirect chain looked like this:

1. "https://tr.ee/vocal-media"

2. "https://tinyurl.com/vocal-media"

3. "https://merchant.528431970.sbs/r9cgmw4gv"

4. "https://httpbin.org/"

The reported serving IP address was:

44.209.237.184

The security report showed that 2 out of 93 vendors flagged the submitted URL as malicious.

And the report included the classification Phishing and Other Frauds.

Now, I wasn't about to stop there.

INVESTIGATION NUMBER TWO: SOMEBODY CHANGED THE ROUTE.

During the subsequent investigation, I encountered another version of the suspicious link.

This time, the URL was:

"https://tr.ee/vocal-verify"

And the redirect chain had changed:

1. "https://tr.ee/vocal-verify"

2. "https://tinyurl.com/25nhxe3z"

3. "https://merchant.692047518.sbs/fqajr5uc9"

4. "https://httpbin.org/"

The reported serving IP address was:

3.221.253.123

Now, let's compare those two investigations.

The original intermediate domain was:

"merchant.528431970.sbs"

The newer intermediate domain was:

"merchant.692047518.sbs"

Different domain numbers.

Different URL paths.

Different shortened-link destination.

And a different reported serving IP address.

I don't know about y'all, but somebody appears to have updated the itinerary.

And I have the receipts.

INVESTIGATION NUMBER THREE: BECAUSE I WANTED TO CHECK AGAIN.

Now, here's where I decided to submit the same newer URL more than once.

The first scan was recorded at 12:16:47 UTC on November 15, 2026.

The second scan was recorded at 13:38:39 UTC.

Both returned the same information.

Same redirect chain.

Same final destination.

Same reported serving IP:

3.221.253.123

So, naturally, I decided to check it again.

At 14:16:44 UTC, I ran another scan.

And THIS TIME?

54.172.45.38

EXCUSE ME?

Now we have three different reported serving IP addresses across the investigations:

- Original: 44.209.237.184

- Subsequent: 3.221.253.123

- Latest: 54.172.45.38

Here's the interesting part.

The latest redirect chain remained the same as the previous scan, but the reported serving IP address changed.

I cannot tell you exactly why that happened. Different hosting configurations, load balancing, or other network arrangements can produce different serving IP addresses.

But I can tell you what the reports showed.

And I'm documenting it.

Because apparently, somebody thought I wasn't going to notice.

Baby, I went back and found the original screenshot.

You thought I wasn't keeping receipts?

Please.

AND WEBROOT IS STILL GIVING ME THAT LOOK.

The latest security report included these classifications:

- alphaMountain.ai: Information Technology

- Bitdefender: Education

- Sophos: Information Technology

- Webroot: Phishing and Other Frauds

- Forcepoint ThreatSeeker: Web Hosting

- Google: Technology

Now, I'm not claiming every vendor independently confirmed a phishing operation.

But Webroot's classification is certainly worth noting.

PHISHING AND OTHER FRAUDS.

Well, damn.

And before anybody gets confused about the final destination, HTTPBin is a legitimate HTTP testing service. Its appearance at the end of the redirect chain does not establish that HTTPBin is involved in anything suspicious.

The concern is the suspicious verification message, the unfamiliar intermediate domain, and the overall redirect trail.

Because why are we taking a damn road trip to verify a Vocal Media account?

Where are we going?

Do I need a passport?

Is there a layover?

Are we stopping for gas?

Can somebody at least tell me whether there's complimentary Wi-Fi?

I thought we were verifying an account, not taking a vacation through the internet.

VOCAL WRITERS, PLEASE PAY ATTENTION.

During my original investigation, other writers started reporting similar activity.

One writer reported suspicious comments on nearly 100 stories.

And remember, my first round involved 23 of my own stories.

That's a lot of opportunities for somebody to convince writers that their accounts are in trouble.

And that's what concerns me.

I don't know who's behind these accounts.

I don't know whether anybody has successfully had their account compromised.

I don't know the ultimate purpose behind every variation of these links.

But I do know that impersonating platform support and directing writers to suspicious verification links is something we should take seriously.

Don't click those links.

Don't provide your Vocal password.

Don't enter debit-card information.

Go directly to Vocal Media through its official website if you have questions about your account.

Save screenshots.

Document usernames.

Keep suspicious URLs.

Report the comments.

And tell other writers when you encounter something.

We can look out for one another.

Because the last thing anybody needs is to lose access to years of writing because they trusted somebody pretending to be customer support.

AND JUST LIKE THAT... BORIS AND NATASHA HAVE LEFT THE BUILDING!

Now, here's where things get REALLY interesting.

After this latest round of suspicious comments, I went back to check on the situation.

And guess what?

THE COMMENTS ARE GONE.

The account pretending to represent Vocal Support?

GONE, TOO!

Well, DAMN.

That was quick.

Now, I don't know what happened behind the scenes. I can't tell you whether Vocal Media removed the account, whether other writers reported it, or whether whoever was behind it decided to pack up and disappear.

But I can tell you something.

This time, the account disappeared even quicker than it did during the first round.

And I'm certainly not complaining.

I was just getting comfortable in my new investigative position, and now my suspects have disappeared.

Did somebody finally check the guest list?

Did the bouncer recognize them from their previous visit?

Did the Plastics have an emergency meeting?

Did Gretchen finally get tired of seeing these two trying to sit at the table?

I don't know.

But if Vocal Media is taking action against these impersonation accounts, I absolutely welcome it.

Because that's what we wanted in the first place.

We want writers to be able to publish their work without worrying about somebody impersonating platform support and trying to collect their personal or financial information.

And if the comments and account are gone, that's a development worth documenting.

THE FINAL WORD.

I came to Vocal Media to write.

I didn't come here to become an unpaid employee of the Internet Police Department.

I have stories to tell, articles to publish, contests to enter, and a writing portfolio to build.

But when somebody starts messing with my work, I'm going to pay attention.

And if I can use publicly available tools to examine suspicious links and share what I find with other writers, then that's exactly what I'm going to do.

Pinky and the Brain had their run.

They tried to take over the world.

Now Boris and Natasha have apparently decided they want to take over the comment section.

But I have news for them.

THE GUEST LIST HAS BEEN CHECKED.

The blue check marks are visible.

The V+ badges are visible.

The community is still here.

And you two?

You're still outside.

How you gonna hate from outside of the club? You can't even get in!

LEGGO!

And as for that cafeteria table?

You already know what the answer is.

YOU CAN'T SIT WITH US!

Not in our comment sections.

Not pretending to be Vocal Support.

And certainly not trying to get access to our accounts.

The comments are gone. The account is gone. And I hope the next time somebody tries this nonsense, they get stopped just as quickly.

Now, if you'll excuse me, I have actual stories to write.

But Boris and Natasha, if you decide to make another appearance?

Please understand something.

I have already retired one set of cartoon villains.

I have room for a sequel.

And apparently...

BITCH, I GOT TIME TODAY.

— Dakota Denise

cybersecurityhackers

About the Creator

Dakota Denise

Every story I publish is real lived, witnessed, survived, by myself or from others who trusted me to tell the story. Enjoy 😊

Enjoyed the story? Support the Creator.

Subscribe for free to receive all their stories in your feed. You could also become a paid subscriber, letting them know you appreciate their work.

Subscribe For Free

Reader insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment
    Written by Dakota Denise