The dash was treated as a special character when chaining properties in the generated k6 code. The maintainer confirmed the cause and shipped a fix, so upgrading postman-to-k6 to 1.8.5 or later resolves the mangled auth headers.

Context: GitHub issue on apideck-libraries/postman-to-k6: converting a Postman collection to k6 mangles authorization keys that contain a dash character, e.g. an x-api-key style header becomes a broken chained expression.