bad actors targeted exchange- /owa/auth/x.js

Copper Contributor



Most of the attacks were reconnaissance attempts. A significant number of these were against systems that did not run Exchange in the backend:

• /owa/auth/x.js


Also, we find it from the bad actors targeted exchange and successfully got the below output: • HTTP 200: Success Reply - OK • /owa/auth/x.js • Response Code 302 (HTTP response status code 302 Found is a common way of performing URL redirection) • Access Success(object download )


How I can solve this issue on Exchange and what is this related to? 

0 Replies