Loading story…
Security researchers reported a Python supply-chain attack on PyPI involving sympy-dev, a typosquatted package designed to impersonate the widely used SymPy symbolic mathematics library. The malicious listing copied SymPy’s description and branding and presented itself as a plausible “development” variant, leading to rapid uptake (reported at ~1,000–1,100+ downloads shortly after publication), increasing the likelihood of exposure in developer workstations and CI environments.
Analysis indicates the package’s malicious logic is selectively triggered when certain polynomial routines are executed (e.g., Groebner-basis related functions), reducing the chance of immediate detection. When triggered, the backdoored code retrieves a remote JSON configuration, downloads a threat actor-controlled Linux ELF payload, and executes it in-memory using memfd_create and /proc/self/fd to minimize on-disk artifacts; reporting also identified infrastructure including 63.250.56[.]54. The payload chain ultimately deploys XMRig-based cryptomining on Linux hosts, using techniques previously observed in cryptojacking activity such as FritzFrog and Mimo.
Trace attribution and downstream blast radius.
4 events from the most recent confirmed update back to the earliest known activity.
At the time of reporting, 'sympy-dev' was still available on PyPI despite the discovery, and Socket was reported to have petitioned for its removal.
Security analysis revealed that the malicious code backdoored selected SymPy-like routines, used memfd_create and /proc/self/fd for fileless execution, and could deliver arbitrary second-stage payloads beyond the observed cryptominer.
After publication, the package was downloaded more than 1,100 times and, when specific polynomial routines were invoked, acted as a staged loader that fetched a remote configuration and in-memory ELF payload to deploy XMRig-compatible cryptominers on Linux systems.
A typosquatted Python package named 'sympy-dev' was published to PyPI, impersonating the legitimate SymPy library by copying its description and branding and presenting itself as a plausible development variant.
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.
3 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcesecurityonline.info
Open sourcethehackernews.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.
A typosquatted PyPI package, **sympy-dev**, impersonated the SymPy mathematics library and delivered a staged Linux payload through backdoored polynomial-code paths. Versions `1.2.3` through `1.2.6` fetched remote JSON configuration and ELF binaries from `63.250.56.54` and `185.167.99.46`, then used `memfd_create` and `/proc/self/fd/<fd>` to execute payloads from memory without a conventional on-disk executable. Recovered second-stage payloads were UPX-packed XMRig miners communicating over Stratum TLS, though the loader could run arbitrary code with the Python process's privileges. The campaign illustrates a broader Linux evasion pattern in which attackers execute ELF binaries, scripts, or kernel modules through anonymous memory-backed descriptors, deleted files, or unnamed temporary files. Related techniques include combining `O_TMPFILE` with `execveat(AT_EMPTY_PATH)` to run an ELF from an unnamed file. Defenders should prioritize behavioral telemetry and correlations—including `memfd_create`, execution through `/proc/self/fd`, interpreter process lineage, self-deletion, and `init_module` or `finit_module` calls—rather than relying solely on filesystem artifacts; Elastic Defend 9.4.0 adds relevant telemetry on supported Linux kernels.
Sep 9, 2026
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).
Jun 29, 2026
Security researchers reported multiple **software supply-chain** threats in public package registries where attacker-controlled libraries masquerade as legitimate utilities but install **Windows infostealers**. On NPM, a package named **`duer-js`** (publisher `luizaearlyx`) posed as a console visibility tool and delivered a multi-stage stealer self-identified as **Bada Stealer**; analysis attributed to **JFrog Security Research** described heavy obfuscation, persistence that can survive simple uninstall attempts, and follow-on payload delivery targeting **Discord** by hijacking the desktop client’s startup/injection path to continuously steal data when Discord runs. Separately, Safety’s research team documented **“ExtraZip”**, a campaign of **14 trojanized PyPI packages** impersonating ZIP utilities or mail-sending libraries that deploy a staged infostealer focused on **Telegram Desktop session files**, exfiltrating them via an attacker-controlled **Telegram bot**. The report described **32 layers of obfuscation** and provided an inventory of package names (e.g., `extrazip`, `minizip`, `ziphash`, and multiple `smt*lib` lookalikes) and a timeline of publishing activity across late 2025 through early 2026, indicating sustained, iterative attempts to seed malicious dependencies into developer environments.
Jun 29, 2026