We also faced a similar issue. Looks like someone scanned AWS, connected to all public redis servers, and possibly ran “CONFIG SET REQUIREPASS ””, thus locking down the running instance of redis. Once you restart redis, the config is restored to normal.
Best thing would be to use AWS security group policy and block port 6379 for public.