INJECTIVE SDK COMPROMISED ON NPM WITH WALLET STEALER

The Injective Labs development team discovered that their SDK project on GitHub had been breached, allowing attackers to deploy a trojanized version of the package to the Node Package Manager registry. Developers who installed the compromised SDK package unknowingly exposed their cryptocurrency wallet credentials. The malicious code extracted private keys and mnemonic seed phrases—critical data needed to access and control blockchain wallets—and transmitted them to attacker-controlled servers. Injective Labs immediately notified the npm security team after identifying the breach. npm removed the malicious package and suspended the affected project. The team released a statement warning developers to review their wallet security if they installed the SDK during the compromise window. Recommended Actions: - Check installation logs for the compromised SDK versions - Rotate wallet private keys and regenerate seed phrases if exposed - Monitor linked wallets for unauthorized transactions - Update to the official patched version once released This incident reflects a broader vulnerability in open-source software distribution. Package repositories like npm, PyPI, and RubyGems remain frequent targets for supply chain attacks because a single compromised project can affect thousands of downstream users. Injective Labs has since implemented additional security measures including enhanced GitHub repository protections and two-factor authentication requirements for npm publishing. The incident underscores the importance of developer vigilance when installing third-party packages, particularly those requiring sensitive credentials. No official statement has specified the exact number of affected users or whether any wallets were successfully drained. Developers are advised to monitor their security advisories and consider using dependency scanning tools to detect compromised packages in their projects.