What 45% Means: Securing the Code Your AI Agents Just Wrote

July 6, 2026
July 6, 2026

0 min read

AI Security
What 45% Means: Securing the Code Your AI Agents Just Wrote

@injectivelabs/sdk-ts version 1.20.21, published to npm on June 8, 2026 and disclosed by Socket's research team on July 9, 2026, is a malicious release of the official Injective Labs TypeScript SDK that exfiltrates wallet private keys and mnemonic phrases through a disguised telemetry function. The compromised version hooked the SDK's wallet-generation code, so any application that derived a wallet while running it had that wallet's secret material sent to an attacker-controlled endpoint. No CVE has been assigned to this incident as of publication; it is tracked as a malicious npm package release.

This post covers what happened, how the payload executed, every affected package and version, the indicators of compromise, and the first-hour response steps for any team with @injectivelabs/sdk-ts or another @injectivelabs-scoped package in its dependency tree

Attack Summary

  • Affected package: @injectivelabs/sdk-ts
  • Malicious version: 1.20.21
  • Clean version: 1.20.23
  • Ecosystem: npm
  • Vulnerability class: wallet private key and mnemonic theft via a disguised telemetry function
  • Weekly downloads: approximately 50,000
  • Dependent packages: 87
  • Malicious version downloads: 310
  • Disclosed by: Socket Security, July 9, 2026
  • CVE: none assigned as of publication

Background

@injectivelabs/sdk-ts is the official TypeScript SDK for Injective Labs Cosmos-based Layer-1 chain. It is the standard library node services, exchanges, and wallets use to derive addresses, build transactions, and query the chain, which is why a compromise in its wallet-generation path has outsized reach across the Injective ecosystem. The package sits in the dependency tree of dozens of downstream Injective tooling packages, so teams can be exposed even when they never installed it directly.

Table of contents

Related blogs

Navigating 2026 AI Risk Regulations

Navigating 2026 AI Risk Regulations

The EU delayed high-risk AI obligations to 2027 and 2028, then switched on enforcement. Here is what 2026 AI regulation actually requires, and why most of it comes down to what your agents can reach.

August 12, 2026

13

The Hidden Security Cost of Self-Hosting Kimi, DeepSeek, and Qwen

The Hidden Security Cost of Self-Hosting Kimi, DeepSeek, and Qwen

Open-weight models cut inference costs by 60 to 90 percent. They also turn AI into infrastructure the security team has to discover, secure, and continuously verify.

July 30, 2026

12

Application Security in the Post-Autonomous-Exploit Era

Application Security in the Post-Autonomous-Exploit Era

OpenAI's models escaped a sandbox and hacked Hugging Face mid-evaluation. What that means for how application security has to work next.

July 22, 2026

8

Stop the waste.
Protect your environment with Kodem.

A Primer on Runtime Intelligence

See how Kodem reads what actually loads and executes in your running applications, and why that changes which findings matter.

See the Kodem platform

Kodem shows which vulnerabilities actually load and execute in your running applications, so your team works the risk that is real.

The State of the Application Security Workflow

This report aims to equip readers with actionable insights that can help future-proof their security programs. Kodem, the publisher of this report, purpose built a platform that bridges these gaps by unifying shift-left strategies with runtime monitoring and protection.

3D book mockup of Kodem's State of the Application Security Workflow 2025 report

Get real-time insights across the full stack…code, containers, OS, and memory

Watch how Kodem’s runtime security platform detects and blocks attacks before they cause damage. No guesswork. Just precise, automated protection.

Kodem issues list with a magnified view of insight icons: runtime, ingress, and exploitability
Combined author
Mahesh Babu
Publish date

0 min read

AI Security