Using the packages results in the account being locked by Steam Support?

[PineapplePizza]

Hello All.

I have started to develop a steam bot that uses the "node-steamcommunity" and "node-tf2" packages, but upon logging in to the bot with a Steam account - the account used becomes locked by Steam Support and when viewing the profile used by the bot while logged into Steam shows the message "Steam Support suspects your account may have been accessed by someone else. We are temporarily forcing your profile private as a security precaution. Please contact Steam Support so we can assist you. "

This issue only occurs when i login with the bot. The bot performs nothing at the moment besides logging into Steam and setting the account as "EPersonaState.Online" and playing Team Fortress 2 in the "loggedOn" event.

Here are my login options used by the bot:

const SteamLoginOptions = {
    accountName: env.steam.username,
    password: env.steam.password,
    twoFactorCode: Steam2FA.generateAuthCode(env.steam.sharedSecret),
    dataDirectory: 'C:/steam_data',
    savePollData: true,
    machineIdFormat: SteamUser.EMachineIDType.PersistentRandom
};

Please help in figuring out what i am doing wrong, this is getting quite annoying as i have already contacted Steam Support various times to unlock the account used by the bot.

[Dr. McKay]

Doesn't look like you're doing anything wrong from those login options. The IP you're logging in from is probably just really suspicious.

[PineapplePizza]

It is quite strange, as i can sign into Steam on the IP used by the bot (either via the PC client or the website) and perform actions and play games without getting the account locked if i do not use the bot. It is only when i use the bot, that the account will become locked after the bot logs in to Steam...

Please advise on how to avoid this (like using the same machineId of my PC client or something) - it is really quite annoying to have to deal with these things...