#spoofed

2025-01-25

Ok, this is a thing for anyone still on the xtwitter.

“Ads featuring fake CBC articles have inundated the social media platform X in recent weeks. The ads are designed to lure Canadians into a sophisticated scam that uses Russian internet infrastructure, CBC News has found. 

CBC News' visual investigations unit has investigated both the internet infrastructure behind the ads — leading from a Barrie, Ont., provider, to the Netherlands, to Russia — as well as the spoofed accounts from local businesses sharing the ads.”

cbc.ca/news/canada/cbc-ads-fak

#disinformation #CBC #Fraud #Fakes #Advertising #Spoofed

Steve Dustcircle 🌹dustcircle
2024-09-05
2024-06-06

In the years since, many attacks have been created.

One example is DNS cache poisoning, where the attacker exploits flaws of DNS resolvers & make them cache incorrect IP addresses, causing clients to connect to hosts.

This reveals one vulnerability of DNS: it is unauthenticated.

Traditional DNS clients today have no way to validate answers, so they can easily be .

2024-05-05

@Edent This response by does almost nothing to help , in fact it's a free "suckers list" for scammers to use as caller ID

The simplest message to customers is to use ONE reception number, and repeat it in every text, popup, webpage, and ask customers to protect themselves by adding it to their contacts and ALWAYS presume you are talking to a criminal unless you called that number

There is no other practical advice that works

hawaiianeye797 (Craig F)hawaiianeye797@mastodon.online
2023-07-18

Author of spoof story shared by Greg Abbott calls him one of ‘dumbest people in the country’

theguardian.com/us-news/2023/j #GregAbbott #spoofed

2023-01-26

#infosec

#Hackers often use this clever trick to take you to #phishing sites — can you spot it?

These #spoofed URLs look quite similar to legitimate ones at first glance.

Which one of these is real?

How to stay safe from spoofed URLs: tomsguide.com/news/hackers-oft

Sean Whalen 👨🏼‍🦼🏳️‍🌈🇺🇦🕊️seanthegeek@infosec.exchange
2023-01-07

In the short time I've been in the #Mastodon #Fediverse so far, I've talked a lot about how #DMARC can help prevent #spoofed #emails from being delivered to their targets, in light of a wave of Mastodon-themed phishing. That made me wonder, "How many Mastodon instances have a DMARC record on their domain? How many of those are set up to properly?" For their own security Users should join servers with an enforced DMARC policy, and instance admins should enforce DMARC on their domains to protect users and attract a security conscious userbase.

I wrote a script that queries instances.social for the 1000 top Mastodon instances based on the number of active users, feeds that list to #checkdmarc to query for, parse, and validate DMARC #DNS records. Here are the results.

github.com/seanthegeek/mastodo

As of earlier today, 148 instances with a combined 295, 975 active users had an enforced DMARC policy (p=quarantine or p=reject). 113 instances with a combined 168,965 active users have deployed a monitor only policy, 3 instances with a combined 577 active users have an invalid DMARC record, and 113 instances with a combined 486,972 active users don't have any DMARC record.

As I looked through the list of instances, I noticed that infosec.exchange is now the 7th largest Mastodon instance on the public internet, with 18,328 active users (and counting. Thanks @jerry!

#Infosec #InformationSecuriy #phish #phishing #spoofing #adminsofmastodon #OpenSource #OpenSourceSoftware #FLOSS #Python #CLI #API

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst