MailGuard spontaneous activation

[PREFIRE]

Hello!

Previously, my software had authorization of a newly registered account followed by saving authorization cookies via the following code:
 

const client = new (require('steam-user'))({
[`${[[PROXY_TYPE]].toLowerCase()}Proxy`]: [[PROXY_STRING]],
});

[[COOKIES]] = await(new Promise((resolve, reject) => {
    client.on('webSession', (_, cookies) => {
        resolve(cookies);
    });

    client.on('error', reject);

    client.logOn({
        accountName: [[LOGIN_STEAM]],
        password: [[PASSWORD_STEAM]],
    });
}));

but after some time I noticed that after such authorization - Steam turns on MailGuard spontaneously (if at the same time to fill out the profile, through requests, then turning on MailGuard - 100%).

In the same order of actions, but through emulation (I do everything through BAS) - MailGuard is not spontaneously enabled

I am wondering if there is any way to fix this so that MailGuard is not turned off all the time?

Or, is it possible to do authorization via steam-session, since I get RefreshToken after registering an account?

Here's an example of Steam's response after registering:
 

{"bSuccess":true,"bInSteamClient":false,"eresult":1,"refresh_token":"eyAidHlwIjogIkpXVCIsICJhbGciOiAiRWREU0EiIH0..."}

Many thanks!

Edited October 23, 2023 by Dr. McKay
Removed PII refresh token

[Dr. McKay]

I'm not sure what circumstances automatically enable email Steam Guard. If you already have a valid refresh token, then yeah, you can use steam-session to get new cookies.

[4049_1572836826]

Mail guard is activated after the first steam-user / steam app logOn, this refresh_token is only for web uses.