Weird and wonderful compilation of strange bird noises.
Imagine if they find Luigi innocent and he has to go through the rest of his life as That Guy Who Got Turbodoxxed That One Time Because Everyone Thought He Was An Assassin.
Cybercriminals are abusing Google’s infrastructure, creating emails that appear to come from Google in order to persuade people into handing over their Google account credentials. This attack, first flagged by Nick Johnson, the lead developer of the Ethereum Name Service (ENS), a blockchain equivalent of the popular internet naming convention known as the Domain Name System (DNS). Nick received a very official looking security alert about a subpoena allegedly issued to Google by law enforcement to information contained in Nick’s Google account. A URL in the email pointed Nick to a sites.google.com page that looked like an exact copy of the official Google support portal.
As a computer savvy person, Nick spotted that the official site should have been hosted on accounts.google.com and not sites.google.com. The difference is that anyone with a Google account can create a website on sites.google.com. And that is exactly what the cybercriminals did. Attackers increasingly use Google Sites to host phishing pages because the domain appears trustworthy to most users and can bypass many security filters. One of those filters is DKIM (DomainKeys Identified Mail), an email authentication protocol that allows the sending server to attach a digital signature to an email. If the target clicked either “Upload additional documents” or “View case”, they were redirected to an exact copy of the Google sign-in page designed to steal their login credentials. Your Google credentials are coveted prey, because they give access to core Google services like Gmail, Google Drive, Google Photos, Google Calendar, Google Contacts, Google Maps, Google Play, and YouTube, but also any third-party apps and services you have chosen to log in with your Google account. The signs to recognize this scam are the pages hosted at sites.google.com which should have been support.google.com and accounts.google.com and the sender address in the email header. Although it was signed by accounts.google.com, it was emailed by another address. If a person had all these accounts compromised in one go, this could easily lead to identity theft.
Don’t follow links in unsolicited emails or on unexpected websites.
Carefully look at the email headers when you receive an unexpected mail.
Verify the legitimacy of such emails through another, independent method.
Don’t use your Google account (or Facebook for that matter) to log in at other sites and services. Instead create an account on the service itself.
Technical details Analyzing the URL used in the attack on Nick, (https://sites.google.com[/]u/17918456/d/1W4M_jFajsC8YKeRJn6tt_b1Ja9Puh6_v/edit) where /u/17918456/ is a user or account identifier and /d/1W4M_jFajsC8YKeRJn6tt_b1Ja9Puh6_v/ identifies the exact page, the /edit part stands out like a sore thumb. DKIM-signed messages keep the signature during replays as long as the body remains unchanged. So if a malicious actor gets access to a previously legitimate DKIM-signed email, they can resend that exact message at any time, and it will still pass authentication. So, what the cybercriminals did was: Set up a Gmail account starting with me@ so the visible email would look as if it was addressed to “me.” Register an OAuth app and set the app name to match the phishing link Grant the OAuth app access to their Google account which triggers a legitimate security warning from no-reply@accounts.google.com This alert has a valid DKIM signature, with the content of the phishing email embedded in the body as the app name. Forward the message untouched which keeps the DKIM signature valid. Creating the application containing the entire text of the phishing message for its name, and preparing the landing page and fake login site may seem a lot of work. But once the criminals have completed the initial work, the procedure is easy enough to repeat once a page gets reported, which is not easy on sites.google.com. Nick submitted a bug report to Google about this. Google originally closed the report as ‘Working as Intended,’ but later Google got back to him and said it had reconsidered the matter and it will fix the OAuth bug.
https://www.fsis.usda.gov/recalls-alerts/cargill-kitchen-solutions-recalls-liquid-egg-products-due-unapproved-substance
WASHINGTON, March 28, 2025 – Cargill Kitchen Solutions, a Lake Odessa, Michigan establishment, is recalling approximately 212,268 pounds of liquid egg products that may contain a cleaning solution with sodium hypochlorite, the U.S. Department of Agriculture’s Food Safety and Inspection Service (FSIS) announced today. The liquid egg items were produced on March 12 and 13, 2025. The following products are subject to recall: -32-oz. (2-lb.) carton containing “egg beaters ORIGINAL LIQUID EGG SUBSTITUTE” and USE BY AUG 10 2025. -32-oz. (2-lb.) carton containing “egg beaters CAGE-FREE ORIGINAL LIQUID EGG SUBSTITUTE” and USE BY AUG 09 2025. -32-oz. (2-lb.) carton containing “egg beaters CAGE-FREE ORIGINAL FROZEN EGG SUBSTITUTE” and “egg beaters NO ENJAULADAS ORIGINAL SUSTITUTO DE HUEVO CONGELADO” and USE BY MAR 07 2026. -32-oz. (2-lb.) carton containing “Bob Evans Better’n Eggs Made with Real Egg Whites” and USE BY AUG 10 2025.
The products subject to recall bear establishment number “G1804” ink-jetted on the carton. These items were shipped to distributor locations in Ohio and Texas and for foodservice use in Arizona, California, Colorado, Florida, Illinois and Iowa. There is a possibility that the products were distributed nationwide.
some emphasis mine.
sodium hypochlorite is a type of bleach.
so once again we have a recall where the company responsible does not actually know all of where its products wound up. which is bad, because bleach is in them. the list of affected states is not comprehensive.
if you use these products in these sizes at all, anywhere in the US, check your cartons.
The problem was discovered when FSIS received a tip about the potential contamination of these products. After conducting an investigation and thorough assessment of the contents of the cleaning solution, FSIS scientists concluded that use of this product should not cause adverse health consequences, or the risk is negligible, resulting in a Class III recall. Although FSIS does not expect any adverse health effects for Class III recalled products and there have been no confirmed reports of adverse reactions due to consumption of these products, anyone concerned about an illness should contact a healthcare provider.
FSIS is concerned that some product may be in consumers’ or foodservice refrigerators or freezers. Consumers who have purchased these products are urged not to consume them and foodservice locations are urged not to serve them. These products should be thrown away or returned to the place of purchase.
some emphasis mine.
the manufacturer did not catch their own contamination. someone sent a tip to the FSIS, who investigated and found that yes, this shit is contaminated with a cleaning solution that contains bleach.
although you probably do not want to eat these on purpose, the FSIS insists that the contaminated products are probably not going to cause major health issues, and none had been reported when the recall was announced. but it is worth pointing out that a lot of these products went to foodservice, and most people making or ordering an omelette do not think they are about to eat fucking bleach.
if you got sick after ordering an egg dish, reach out to appropriate foodservice staff and ask if they use these products.
if you think eating the contaminated products may have hurt you, talk to your doctor.
more information about this recall, including who to contact about problems, questions, or safety concerns can be found through the FSIS link.
Link to bypass paywall if necessary
my mans running animation only got two frames