Usage of this library causes account to enter a "compromised" state

[ianw11]

Since updating to 3.48.8, logging in causes my account to get flagged by Steam as "compromised".

A red notification shows up in the title bar saying "an unknown device has logged in from " and I have to go through Steam Support to unlock the account. This involves resetting my password and even unlinking and relinking my Steam Authenticator.

I don't know if this is affecting anybody else, but at this point I cannot log in. Is there a header field I need to specify to indicate "this is a trusted device"? Is the PiHole on my network causing issues?

[Revadike]

That's concerning

[ianw11]

It appears others are experiencing this as well, but I might migrate this issue over to the steam-session repo

https://dev.doctormckay.com/topic/5758-i-get-my-account-banned-when-i-log-in-with-a-qr-code/

[lnickersl]

This might not be related to your issue, but I had this happen to me few weeks ago. I had my trading account that I browse from my personal PC.
Then I launched a script from a VPS in a different country to automate some trades and it got flagged as compromised, my password got reset which resulted in a 5 day trade ban. After 5 day trade ban I tried again and got restricted again.

In recent days it didn't happen again.