Loading story…
A malicious release of the npm package @injectivelabs/sdk-ts (v1.20.21) was published in a software supply-chain attack that embedded infostealer functionality to capture cryptocurrency wallet private keys and mnemonic phrases. The tainted code was introduced through commits to Injective Labs’ official GitHub repository using a contributor account with prior project history, then shipped to npm, where it hooked wallet key-generation functions during normal library use, base64-encoded the captured secrets, and exfiltrated them in POST requests to an Injective Labs public infrastructure endpoint to blend with legitimate traffic.
The compromise extended beyond the core package through dependency poisoning: attackers published 17 additional @injectivelabs scoped packages pinned to the malicious SDK version, and reporting identified 87 dependent packages in scope with a combined 112,378 downloads. Although the malicious sdk-ts release was reportedly downloaded about 310 times before detection and rollback, the compromised npm version and GitHub release artifacts remained available at the time of reporting. Developers were urged to upgrade to 1.20.23, audit direct and transitive @injectivelabs dependencies, and treat any mnemonic phrases or private keys processed by affected versions as compromised.
Trace attribution and downstream blast radius.
8 events from the most recent confirmed update back to the earliest known activity.
SlowMist reported that the malicious code in @injectivelabs/sdk-ts v1.20.21 was embedded in wallet key derivation functions and triggered by generate(), fromMnemonic(), and string-based fromHex() calls. The stolen secrets were Base64-encoded and sent in the X-Request-Id header of empty HTTP POST requests disguised as gRPC-Web traffic to an Injective-domain hostname.
Reporting on the supply-chain attack said 17 additional @injectivelabs scoped packages were configured to depend on the compromised @injectivelabs/sdk-ts@1.20.21 release, expanding downstream exposure through transitive dependencies. This quantified the breadth of package propagation beyond the initially disclosed malicious SDK package.
Researchers said the supply-chain attack occurred after attackers gained access to a legitimate contributor's GitHub account and used the normal release workflow to publish the compromised @injectivelabs/sdk-ts package. This added new technical detail about how the malicious npm release was introduced.
The @injectivelabs/sdk-ts compromise was publicly reported in GitHub issue #697. This marked a public disclosure of the incident separate from the malicious publication, revert, and clean package release.
A clean version of the package, 1.20.23, was published shortly after the malicious release was reverted. Developers were advised to upgrade and treat any keys or mnemonic phrases processed by affected versions as compromised.
The malicious activity was detected and reverted quickly on the night it began. This rapid response appears to have limited impact, with the compromised npm version reportedly downloaded 310 times.
A malicious version of @injectivelabs/sdk-ts (v1.20.21) was published to npm as part of a supply-chain attack. The attacker also caused additional @injectivelabs packages to depend on the compromised version, expanding exposure across the ecosystem.
Malicious activity involving the npm package @injectivelabs/sdk-ts version 1.20.21 began on June 8, 2026. The compromised package contained code that captured wallet private keys and mnemonic phrases and exfiltrated them to an InjectiveLabs public infrastructure endpoint.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 12 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
9 references tracked. Mallory keeps watching after this page renders.
slowmist.medium.com
Open sourcecysecurity.news
Open sourcethehackernews.com
Open sourcecysecurity.news
Open sourceox.security
Open sourcethreats.wiz.io
Open sourcesocket.dev
Open sourcesecuritylabs.datadoghq.com
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Threat actors are using **malicious npm packages** to steal developer credentials and CI/CD secrets, enabling rapid escalation into cloud environments. Google reported that **UNC6426** leveraged keys stolen during the earlier compromise of the *nx* npm ecosystem to pivot from a stolen developer GitHub token into **AWS administrative access within 72 hours**, abusing **GitHub-to-AWS OpenID Connect (OIDC) trust** to create a new admin role. The actor then used that access to **exfiltrate data from AWS S3** and conduct **destructive actions** in production cloud environments; the initial *nx* compromise involved a GitHub Actions `pull_request_target` workflow abuse (“**Pwn Request**”) that enabled publishing trojanized packages containing a `postinstall` chain that executed the **QUIETVAULT** JavaScript credential stealer and uploaded stolen data to a public GitHub repo (`/s1ngularity-repository-1`). Separately, researchers reported new waves of the **PhantomRaven** npm supply-chain campaign distributing **88 additional malicious packages** (via ~50 disposable accounts) that target JavaScript developers by exfiltrating secrets from files like `.gitconfig` and `.npmrc`, environment variables, and CI/CD tokens (e.g., GitHub/GitLab/Jenkins/CircleCI). The campaign uses **slopsquatting** (LLM-suggested lookalike package names) and a stealth technique called **Remote Dynamic Dependencies (RDD)**, where `package.json` pulls a dependency from an external URL so the malicious payload is fetched at install time (`npm install`) and can evade static package inspection; researchers indicated many of these packages remained available in the npm registry at the time of reporting.
Jun 29, 2026
A software supply chain compromise hit the JavaScript ecosystem after malicious versions of **Keyv** and related npm packages were published through legitimate maintainer workflows, with `keyv@6.0.0` identified as a primary malicious release. Researchers said the tainted packages added a `preinstall` hook that executed attacker code during dependency installation on developer workstations and CI runners, while some repositories also contained malicious **VS Code** and **Claude Code** configuration files that could trigger execution when a cloned project was opened. Early community reports tied the incident to the `jaredwray/cacheable` package set and warned that numerous downstream dependencies were exposed. Analysis found the malware targeted high-value secrets including **GitHub** and **npm** tokens, cloud credentials, Vault tokens, Kubernetes service account tokens, SSH keys, and TLS certificates, with tradecraft resembling the **Shai-Hulud** malware family. Investigators reported no evidence that npm itself was breached; instead, the attackers appear to have used stolen maintainer credentials and trusted GitHub Actions publishing pipelines with valid provenance and npm attestation, demonstrating that provenance verified the build source but not whether the source had already been maliciously altered. Responders were urged to avoid affected versions, isolate any host that installed them, remove persistence such as `gh-token-monitor`, and rotate exposed credentials from a clean system.
Aug 8, 2026
Security researchers have uncovered multiple campaigns involving malicious npm packages designed to steal developer credentials and sensitive information from Windows, macOS, and Linux systems. In one operation, ten typosquatted packages impersonated popular libraries such as TypeScript, discord.js, ethers.js, and others, using sophisticated obfuscation, fake CAPTCHA prompts, and postinstall hooks to deploy an information stealer that harvested credentials from system keyrings, browsers, and authentication services. The malware executed in a new terminal window to evade detection and sent stolen data, including IP addresses, to external servers. Another large-scale campaign, dubbed 'PhantomRaven,' involved 126 npm packages and over 86,000 downloads, targeting authentication tokens, CI/CD secrets, and GitHub credentials. These packages leveraged remote dynamic dependencies to fetch and execute payloads during installation, profiling infected devices and exfiltrating secrets for potential supply chain attacks. The attackers employed techniques such as slopsquatting, where AI-generated package recommendations led developers to install non-existent, malicious packages. Some packages impersonated tools from GitLab and Apache, and many remained available on npm at the time of reporting. The campaigns highlight the ongoing risks in the npm ecosystem, with attackers exploiting both user trust and platform weaknesses to compromise developer environments and CI/CD pipelines. Security experts warn that the theft of tokens and credentials could enable further attacks, including the introduction of malicious code into legitimate projects and broader supply chain compromises.
Jun 29, 2026