Log4jAttackSurface VS eth-phishing-detect

Checkout this link for knowing Log4j impact on manufacturers https://github.com/YfryTchsGD/Log4jAttackSurface

Just look at the currently ongoing insanity that is the log4j exploit, and how one single exploit has lead to a generic attack that can impact tons of companies. Imagine if a state decided to use voting machines, and someone found this style of exploit in the system.

Last week (Dec 9th) a major vulnerability was discovered in an open source logging project for Java called log4j. The vulnerability called Log4Shell would allow anyone to remotely run arbitrary code if they sent a message in the right format to the server. This is one of the worst attacks your system can be susceptible to and if you are interested in the technical details of the problem, here is an overview. The attack surface of Log4Shell is staggering, Amazon, Apple, Google, and the Apache Server are affected; it can almost not get bigger than this. We will see the real fallout of Log4Shell in the next weeks and months as right now servers worldwide are being scanned and prodded for this vulnerability.

Companies should verify they are not running any exposed Log4j Java code.  Here is a list of impacted 3rd party software for your reference.  If you find a server at risk, there are three potential ways to fix it as follows.

Looking for vendors/software on known lists like https://github.com/YfryTchsGD/Log4jAttackSurface

Blender ist nicht betroffen, #42

It does and was also affected by log4j.

Thanks, sure it isn't complete but it does contain some scary and surprising (at least when first reading, of course the really aren't) things like: https://github.com/YfryTchsGD/Log4jAttackSurface/blob/master/pages/UniFi.md

Apparently there's proof Steam along with many others are vulnerable.

The project is called MATRIX ABYSS, but their website is https://abyssmatrix.world. When I looked up https://matrixabyss.world/ there is an error saying that this website has been flagged for phishing, by metamask eth-phishing-detect. Super sus.

This was an issue with Metamask's fuzzy filtering, see here. The issue has been resolved, and it's been plenty of time for the change to propagate around. Not sure if you need to update your Metamask or clear your cache or something. Unfortunate that it's still causing trouble.

MetaMask already has a blacklist for phishing websites: https://github.com/MetaMask/eth-phishing-detect

Yea, no idea why: https://github.com/MetaMask/eth-phishing-detect/issues/7876

they added sudoswap to their fuzzy list https://github.com/MetaMask/eth-phishing-detect/pull/7633 and that caused issues with other domains with "swap" in the name

According to the code on https://github.com/MetaMask/eth-phishing-detect/blob/45ea5cf..., looks like that everything within Levenstein distance of 3 from whitelisted hosts (like "metamask.*") is blocked.

Metarank and Metamask have the distance of 3. I've made a ticket some time ago in their github repo (https://github.com/MetaMask/eth-phishing-detect/issues/6855), but it seems that it was lost in thousands of similar tickets.

Do you have an old version of Metamask? That site was accidentally picked up by a blacklist regex but was whitelisted again back in october - https://github.com/MetaMask/eth-phishing-detect/pull/5563