As reported by The Hacker News, threat actors successfully compromised the Injective Labs SDK GitHub repository and weaponized it to distribute a malicious npm package designed to silently exfiltrate cryptocurrency wallet private keys and mnemonic seed phrases — some of the most sensitive secrets in the Web3 ecosystem.

Threat Alert: As reported by The Hacker News, threat actors successfully compromised the Injective Labs SDK GitHub repository and weaponized it to distribute a malicious npm package designed to silently exfiltrate cryptocurrency wallet private keys and mnemonic seed phrases — some of the most sensitive secrets in the Web3 ecosystem.

Why This Attack Is More Dangerous Than It Appears

On the surface, this looks like another package-hijacking incident. But the mechanics here deserve closer attention. The attackers didn't just upload a lookalike package — they compromised a trusted, legitimate GitHub repository and used that access to publish a poisoned version of a real, widely-used SDK. That distinction matters enormously. Developers who rely on dependency pinning, provenance checks, or simply "trusting what they know" were directly targeted by this trust relationship.

Embedding the malicious payload inside fake telemetry functionality is a particularly calculated choice. Telemetry code is routinely added to SDKs to collect usage metrics, and most developers neither audit nor question it. It blends into the expected behavior of modern software, making static code review far less likely to catch it before execution.

Who Is at Risk

Why This Attack Is More Dangerous Than It Appears
Web3 / DeFi application developers using the @injectivelabs/sdk-ts package — especially those who updated to version 1.20.21 without auditing the changelog or diff
CI/CD pipelines configured to automatically pull latest package versions — a disturbingly common practice
Institutional or high-value wallets whose private key material was processed by any application built on the compromised SDK version
Downstream users of any application that consumed the trojanized SDK, even if they had no direct npm dependency themselves

The Broader Supply Chain Threat to Web3

The cryptocurrency and Web3 space has become a primary hunting ground for supply chain attackers for a straightforward reason: the payoff is immediate and irreversible. Unlike stealing credentials that require further exploitation to monetize, stealing a wallet's private key or seed phrase translates directly into financial theft — and blockchain transactions cannot be reversed.

"Mnemonic seed phrases are the master keys to cryptocurrency wallets. Any application that processes these values is a high-value target — and any SDK trusted with that data becomes an attack surface worth compromising."

This incident follows a pattern Shield53 has been tracking closely: threat actors are increasingly investing effort into upstream compromises — GitHub accounts, maintainer credentials, CI/CD tokens — rather than publishing lookalike packages. Upstream compromises are harder to detect and carry the full authority of the original project's trust chain.

What Made This Attack Possible

Several structural weaknesses likely enabled this compromise:

  • Insufficient multi-party controls on npm publish permissions tied to the package
  • Lack of mandatory code review or signed releases for SDK versions before npm publication
  • Absence of automated diff-based anomaly detection on new package releases
  • Over-reliance on GitHub repository trust without independent artifact verification

Shield53 Recommendations

Immediate Actions for Developers

  • Audit your dependencies immediately: If your project depends on @injectivelabs/sdk-ts, verify you are not running version 1.20.21. Roll back to the last known-good version and review your lock files.
  • Assume compromise if exposed: Any private keys or seed phrases processed by an application using the malicious version should be treated as compromised. Rotate keys, move funds to new wallets immediately, and conduct a full incident review.
  • Audit recent CI/CD runs: Check build logs for any outbound network connections made during the dependency installation or runtime phase that don't match expected endpoints.
  • Enable npm package provenance checks: Use npm audit and consider tools like Socket.dev or Phylum to flag suspicious package behavior before installation.

Structural Controls to Implement

  • Pin dependencies with integrity hashes in your package-lock.json or yarn.lock and treat any unexpected hash change as a security event requiring review.
  • Require signed releases: Enforce npm package signing and verify signatures as part of your intake process for critical dependencies.
  • Apply least-privilege to npm publish tokens: Publish tokens should be scoped, short-lived, and protected by MFA. No CI/CD system should hold long-lived publish credentials.
  • Monitor for telemetry anomalies: Any SDK that introduces new outbound network calls in a minor version bump should trigger an immediate security review — treat unexpected egress as a red flag, not a feature.
  • Adopt a Software Bill of Materials (SBOM): Maintaining an SBOM allows rapid identification of all projects affected when a compromised package is discovered.

This incident is a reminder that in the Web3 space, the attack surface extends well beyond smart contract code. The developer toolchain — SDKs, npm packages, GitHub integrations — represents a high-value, often under-defended frontier. Organizations building on public blockchain infrastructure should apply the same security rigor to their supply chain that they apply to their on-chain code.