Loading story…
Security researchers reported a supply-chain compromise affecting official dYdX v4 client libraries distributed via npm and PyPI, where attackers published poisoned versions designed to steal cryptocurrency wallet secrets and enable follow-on compromise. The impacted packages were identified as @dydxprotocol/v4-client-js on npm (malicious versions 3.4.1, 1.22.1, 1.15.2, 1.0.31) and dydx-v4-client on PyPI (including 1.1.5post1), which are commonly used by trading bots, automated strategies, and backend services that handle sensitive material such as seed phrases/private keys for signing.
Analysis attributed the distribution method to likely developer account/publishing credential compromise, since the rogue releases were pushed using legitimate publishing credentials. The npm payload embedded logic to exfiltrate wallet seed phrases and a device fingerprint to a typosquatted domain, dydx[.]priceoracle[.]site, enabling correlation of victims across compromises and potentially irreversible cryptocurrency theft; reporting also noted that some infections could backdoor developer devices. The PyPI package was assessed as more severe, combining wallet-stealing with a remote access trojan (RAT) that executes on import and beacons to dydx[.]priceoracle[.]site/py to fetch and run attacker commands (including Windows execution behavior intended to reduce user visibility).
Trace attribution and downstream blast radius.
6 events from the most recent confirmed update back to the earliest known activity.
In related analysis, Aikido highlighted the risk of attackers later claiming package names referenced in documentation but never actually published to npm. The firm recommended mitigations including using npx --no-install and explicitly installing CLI tools.
Security researchers at Socket and Aikido publicly reported that the compromised dYdX packages exfiltrated seed phrases, private keys, and device fingerprints, with stolen data sent to a typosquatted domain resembling dYdX. They warned that both developers and production users could be affected, including through wallet theft and, in some cases, device backdooring.
After receiving responsible disclosure on January 28, 2026, dYdX acknowledged the incident and confirmed that affected npm and PyPI packages had been compromised, while GitHub-hosted versions were not malicious. The company advised users to isolate affected machines, move funds to a new wallet from a clean system, and rotate API keys and other credentials.
Attackers compromised legitimate dYdX-related package publishing accounts and republished malicious versions of @dydxprotocol/v4-client-js on npm and dydx-v4-client on PyPI. The npm payload stole wallet seed phrases and device information, while the PyPI package added remote-access functionality that executed on import and fetched commands from an external server.
The dYdX ecosystem had previously been targeted in 2022 when an npm account hijack led to a compromise of a dYdX-related package. Researchers later cited this as part of a recurring pattern of attacks against dYdX software distribution channels.
At a later, unspecified date after the 2022 npm incident, a dYdX v3-related website was compromised and used to redirect users to phishing pages designed to drain cryptocurrency wallets. This was referenced as another prior attack in the same ecosystem.
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. See the values 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.
2 references tracked. Mallory keeps watching after this page renders.
Map 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.
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.
Jul 15, 2026
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 large-scale supply chain attack has targeted the Node Package Manager (NPM) ecosystem, compromising hundreds of widely used JavaScript packages and threatening the security of software development pipelines globally. In mid-September, cybersecurity researchers identified a self-propagating malware dubbed "Shai-Hulud," which was distributed through trojanized NPM packages, including some with millions of weekly downloads and high-profile packages such as those from CrowdStrike. The attack leveraged a malicious "bundle.js" script that downloaded and executed TruffleHog, a legitimate credential scanner, to harvest developer and CI/CD tokens, cloud service credentials, and environment variables from compromised systems. The stolen credentials were exfiltrated via hard-coded webhooks and GitHub Actions workflows, enabling the attacker to further propagate the malware and gain unauthorized access to sensitive resources. The campaign affected both Windows and Linux systems, increasing its reach and impact across diverse development environments. Sysdig reported that the attack on September 15 involved approximately 200 compromised packages, including @ctrl/tinycolor, and was linked to an attacker who had previously targeted Nx packages in late August. The worm not only stole secrets but also published them publicly on GitHub and attempted to make victim repositories public, amplifying the risk of further compromise. Earlier in the month, other popular packages such as chalk, debug, and duck were also compromised following a successful spear phishing attack against a maintainer, with the attacker seeking to redirect cryptocurrency payments. NPM responded by removing the malicious package versions, but users were required to update or revert to secure versions to mitigate the risk. Sysdig provided same-day threat intelligence and detection capabilities to its customers, including open source Falco rules to identify and respond to the threat. The attack demonstrated the vulnerability of even the most trusted and widely used open source packages, highlighting the importance of continuous monitoring and rapid response in the software supply chain. Security researchers and vendors emphasized the need for organizations to scan their environments for known malicious packages, such as dist.fezbox.cjs, and to review logs for signs of credential exfiltration. The incident underscored the evolving tactics of threat actors targeting developer ecosystems, using advanced techniques to automate propagation and maximize impact. Organizations relying on NPM packages and CI/CD pipelines were urged to remain vigilant, update dependencies promptly, and leverage threat intelligence resources to defend against similar attacks. The Shai-Hulud campaign remains an evolving threat, with ongoing analysis and mitigation efforts by the security community. This incident serves as a stark reminder that popularity and trust in open source packages do not guarantee safety, and proactive security measures are essential to protect software supply chains from compromise.
Jun 29, 2026