The @ts-apis/ts-utils npm package versions 1.0.0 through 1.1.0 contain a deliberately backdoored build in the published dist/index.js file. The malicious payload runs shortly after the package is required, harvesting a broad spectrum of sensitive credentials and configuration files from the local filesystem and environment, including SSH keys, AWS credentials, Kubernetes tokens, Docker config, Git credentials, Google Cloud credentials, and various cloud instance metadata endpoints. The collected data is base64-encoded, chunked, and exfiltrated over HTTPS to a remote server. The malware also maintains a persistent command-and-control channel, polling a remote server every 10 seconds to receive commands or download and execute additional payloads. Sensitive strings are obfuscated to evade detection. The source code repository contains only legitimate TypeScript utilities, indicating the malicious payload was introduced during the build or publishing process. This represents a severe supply chain compromise affecting all listed versions.

Systems with this package installed are fully compromised. The attacker gains access to a wide range of sensitive credentials and secrets stored on the host, including private SSH keys, cloud provider credentials, Kubernetes tokens, and other environment secrets. This enables unauthorized access to cloud resources, source code repositories, container environments, and potentially other infrastructure. The persistent command-and-control channel allows the attacker to execute arbitrary commands and deploy additional malware, leading to complete system takeover. Credential theft and remote control capabilities pose a critical risk to confidentiality, integrity, and availability of affected systems and connected infrastructure.

No official patch or fix is currently available. The package should be immediately removed from all systems. All credentials and secrets stored on affected systems must be considered compromised and rotated immediately from a secure, unaffected environment. Due to the high likelihood of full system compromise, affected hosts should be thoroughly audited and potentially rebuilt to ensure removal of all malicious artifacts. Monitor for any signs of further compromise or lateral movement. Avoid using this package until a trusted, clean version is released and verified.