Rule Definition
Hardcoded passwords in source code should be avoided because they can potentially be retrieved through code inspection and inverse engineering by attackers. Such an attack is difficult to be discovered, and eventually the problem can only be solved at software level thus compromising the usability of the application in the meantime.

Remediation
A non-secure starting patch would be to apply obfuscation techniques to the hardcoded password to prevent reverse-engineering of the generated Python (byte)code. This could be done by hashing the password or constructing the password string in many different places by non-trivial methods. Sensitive data such as passwords should be in principle encrypted and saved in separate files or in a database with restricted user access. Finally one should consider removing backdoors and delegate the password ownership to the end-user.

Violation Code Sample

const password = "WinterIsComing";

// OR

let mypwd;
mypwd = "WinterIsComing";

// OR

login({"password":"WinterIsComing"})

Fixed Code Sample

const password = SafeAccessToPasswordNotReturningAConstValue();

// OR

let mypwd;
mypwd = SafeAccessToPasswordNotReturningAConstValue();

// OR

login({"password":SafeAccessToPasswordNotReturningAConstValue()})

https://cwe.mitre.org/data/definitions/259.html