Malicious npm and PyPI Packages That Use Proxies

Home › Guides › Malicious Proxy Packages

✓ checked 19 October 2026 · source: OpenSSF malicious-packages reports in the OSV.dev database (Apache-2.0), downloaded 19 October 2026 · the packages · method · download the data

Of the 14,514 malicious npm and PyPI package reports in the OpenSSF database so far in 2026, we found 34 that use proxies against the people who install them. 3 turn the computer into a proxy for someone else, 23 are backdoors with a built-in proxy or port forwarding (21 of them from one npm campaign in August), and 8 route the user’s own traffic through someone else’s proxy. The newest, reported on 9 October, is pxnpm, a fake package manager that sends downloads through its author’s registry and proxy.

34 proxy-related malicious packages3 make the computer a proxy21 from one August campaign14,514 malicious reports in 2026

Why proxies show up in malware

Residential proxy networks sell access to home internet connections, so that their customers’ traffic looks like it comes from ordinary households. Some of that capacity comes from bandwidth-sharing apps that people install on purpose and get paid for; we compare what those apps pay in What Your Wi-Fi Is Worth. Security researchers call these apps “proxyware”. The same thing can be done without asking: malware that quietly turns a computer into a proxy exit gives its operator a fresh, clean IP address to use or resell. For botnets that did this at scale, see our residential proxy botnet timeline.

Package registries are an easy way to deliver this. Developers install hundreds of packages, often automatically, and a package can run code the moment it is installed or imported. Attackers publish packages with names close to popular ones, or dress them up as small utilities, and wait for someone to install them. The OpenSSF malicious-packages project collects reports of such packages from security companies and researchers and publishes them in the OSV.dev vulnerability database.

Three ways the packages use proxies

  • Turning the computer into a proxy for others (3). This is proxyware without consent. prosocks, reported on 24 September, registers the computer as a remote-controlled SOCKS5 exit node and adds itself to Windows startup. chrome-stealth, reported on 3 January, says openly that it joins the computer to a proxy network, but it does nothing else; the report says the network’s domain was newly registered and the opt-out didn’t work. permcserver starts a proxy server as soon as it is imported.
  • Backdoors with a built-in proxy (23). Between 4 Aug and 27 Aug, 21 npm packages with names such as streak-math-metrics and hydration-dim-ui hid a remote-access implant that 19 of the reports call RedShell. Besides running commands and, in most reports, stealing credentials and SSH keys, it includes a SOCKS5 proxy, so the operator can reach other machines on the victim’s network through it. Two PyPI packages named like proxy checkers installed a similar backdoor with port forwarding.
  • Routing the user’s own traffic through someone else (8). These don’t sell the victim’s connection; they watch it. pxnpm forces package downloads through its author’s servers, so the author can choose what code gets installed. telegram-helper opens an SSH tunnel to its author’s server and points the system proxy settings at it. Others send Telegram bot tokens, AI coding prompts or web page traffic through relays controlled by the publisher.

The packages

ReportedRegistryPackageTypeWhat the report describes
3 JanPyPIchrome-stealthTurns the computer into a proxy for othersJoins the computer to a proxy network to share its IP address and bandwidth; this is stated, but the package does nothing else and the report says the opt-out does not work.
2 Maynpmcommon-tg-serviceRoutes the user’s own traffic through someone else’s proxyWhen proxying is on, routes the user’s Telegram traffic through SOCKS5 proxies chosen by the author; it also contains a login backdoor.
19 MayPyPImorinRoutes the user’s own traffic through someone else’s proxySends the user’s Telegram bot messages, including the bot token, through a hidden third-party HTTP proxy.
9 JulPyPIproxy-check-iBackdoor with a built-in proxy or port forwardingInstalls a reverse-SSH backdoor that gives a remote operator a shell and TCP port forwarding through the computer.
13 JulnpmpermcserverTurns the computer into a proxy for othersStarts a proxy server as soon as it is imported, turning the computer into a relay that only the author can log in to.
14 JulPyPIproxy-checker-jBackdoor with a built-in proxy or port forwardingInstalls a reverse-SSH backdoor that gives a remote operator a shell and TCP port forwarding through the computer.
15 JulnpmcreditgaugeRoutes the user’s own traffic through someone else’s proxyPoints Claude Code at a third-party endpoint, relaying the developer’s prompts and code through it.
4 Aug – 27 Augnpm21 packages named like streak-*, hydration-* and *-kitBackdoor with a built-in proxy or port forwardingHides a remote-access implant behind a small utility library; the implant includes a SOCKS5 proxy, so the computer can be used to reach other machines.
7 SepPyPItelegram-helperRoutes the user’s own traffic through someone else’s proxyOpens an SSH tunnel to the author’s server and sets the system proxy variables to it, so later traffic passes through that server.
14 Sepnpm@zaka13/thingRoutes the user’s own traffic through someone else’s proxyShips an in-browser proxy kit that routes web page traffic through relays run by the publisher.
14 Sepnpmwebpackbootstrap5Routes the user’s own traffic through someone else’s proxyShips an in-browser proxy kit that routes web page traffic through relays run by the publisher.
14 SepnpmwebpackbootstrapscriptsRoutes the user’s own traffic through someone else’s proxyShips an in-browser proxy kit that routes web page traffic through relays run by the publisher.
24 SepPyPIprosocksTurns the computer into a proxy for othersRegisters the computer as a remote-controlled SOCKS5 exit node, adds itself to Windows startup and reports bandwidth use.
9 OctnpmpxnpmRoutes the user’s own traffic through someone else’s proxyPresents itself as a pnpm-compatible package manager but forces package downloads through the author’s registry and proxy.

“Reported” is the date the report was published in OSV, not the date the package was uploaded. Descriptions are our summaries of the reports, which come mostly from Amazon Inspector and independent researchers. We leave out server addresses and domains. Each package’s OSV ID is in the CSV.

Proxy websites published as npm packages

A separate, larger group isn’t aimed at the person installing it. 110 other 2026 npm reports, 99 of them in July, describe copies of web proxy sites (the kind used to get around school or workplace filters) published as npm packages. They were flagged as malicious, but they work on whoever visits the proxy site, not on the person who installs the package, so we don’t count them above.

What the numbers can’t show

  • These are reports, not convictions. Each entry is a report from a security company or researcher, collected by the OpenSSF project. We describe what the report says.
  • The count is a floor. 4,784 of the 13,043 npm reports this year (37%) contain only a standard warning with no description of what the code does, so proxy behaviour in those can’t be found by reading the reports.
  • Installs aren’t known. The registries don’t publish download counts for packages they have removed, so we can’t say how many people installed these.

Method

On 19 October 2026 we downloaded the full npm and PyPI exports from OSV.dev and kept the malicious-package reports (IDs starting MAL-) published in 2026: 13,043 for npm and 1,471 for PyPI. We searched their text for proxy terms (SOCKS, proxy, exit node, residential, bandwidth, port forwarding, reverse tunnel and the names of bandwidth-sharing apps), which matched 361 reports. We narrowed these to 49 reports whose text describes proxy behaviour, rather than just a package name containing “proxy”, read each one in full, and kept those where the code itself uses a proxy against the installer. We excluded tools that merely carry proxy lists, packages whose only link to proxies is their name, and the web-proxy site bundles described above.

Download the data

  • The 34 packages (CSV): OSV ID, registry, package, report date, type, our summary, who reported it, and a link to the OSV entry. Report data from OpenSSF malicious-packages, Apache License 2.0.

Cite as: ProxyPicker, “Malicious npm and PyPI Packages That Use Proxies”, 19 October 2026, https://proxypicker.com/malicious-proxyware-packages/.

Related: What Your Wi-Fi Is Worth · Residential proxy botnet timeline · Proxy flaws in HTTP libraries.

Press & data requests: email [email protected] for interviews, the raw data behind this page, or corrections. See also our contact page.