Log4Shell was in the wild at least nine days before public disclosure

This article has been indexed from

Security Affairs

Threat actors are already abusing Log4Shell vulnerability in the Log4j library for malicious purposes such as deploying malware. A few hours ago, researchers at NetLab 360 reported that their Anglerfish and Apacket honeypots were already hit by attacks attempting to trigger the Log4Shell flaw in the Log4j library. The attempts were carried out by Muhstik and Mirai botnets in […]

The post Log4Shell was in the wild at least nine days before public disclosure appeared first on Security Affairs.

Read the original article: