Diablo 4 accessing IPs reported to be compromised

Technical Support
1

While playing Diablo 4, all of a sudden every time I try to use a town portal or a waypoint, I am shown the usual loading screen, but it never finishes and I have to kill the game executable. Upon doing this I then see notifications from Malwarebytes saying it has blocked the Diablo 4 executable from accessing a compromised website. These notifications are a list of the following details, basically identical other than the time reported which ranges from :
RTP detection, 03/01/2024 18:10:75 to 18:45:52 (UK local time), compromised, blocked website, 34.38.45.64 port 6113 outbound, D:\Games\Blizzard\Diablo IV\Diablo IV.exe.

On looking this up, this appears to have been happening occasionally for some time to other users, and while some IP blocks get removed, others do not, with Malwarebytes pointing to records in abuseIPDB dot com indicating the IP has recently been abusively used. Since the IP appears to resolve to a googleusercontent domain rather than a Blizzard domain, it is not clear whether Diablo 4 is supposed to be accessing this IP or not.

Game Masters have directed me to this forum to ask the Devs about this. I cannot post the abuseipdb dot com link for the IP address Malwarebytes was reporting but it can be accessed directly and the IP (34.38.45.64) entered to see the results indicating (right now) a 98% confidence of abuse.

Is Diablo4 accessing this IP correct, or is something else going on? If correct, what can be done to stop this occurring, and prevent it from happening again. The answer should not be to whitelist either the IP or Diablo4’s executable.

2

First, I got a real out loud belly laugh at this comment. In other words they sent you to the forum to end the discussion. The Devs do not visit here, and if they did, they never tell us they visit here.

Well, I know they have used Google for some things before. In fact I used to suggest for some that were having issues to setup google dns servers for routing their traffic to fix some issues.

I’m not sure you can fix it. It may not be under your direct control to resolve. Whitelisting it may not help since you have no way to address the actual server IP that is supposedly causing this issue. Unless the IP you are referring to is your own. But I don’t think that’s the case.

This could be a result of either bad traffic routing, or users attacking the game servers and causing or triggering this issue. Blizzard’s games come under attack every day. But most of the time the attacks are small. But occasionally they get hit with larger attacks that can cause outages even. It would not surprise me if something like an attack resulted in this issue. Eventually it should straighten itself out, but that doesn’t help you in the immediate.

1 Like
3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.