← Back
GHSA-6fxh-5965-3xf4
Vulnerability in token-usage-tracker (GHSA-6fxh-5965-3xf4)
Summary
vulnerability in token-usage-tracker (GHSA-6fxh-5965-3xf4). Risk of unauthorized operations or information disclosure. Exploitable via ``asdxzxc``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-6fxh-5965-3xf4** has been found in token-usage-tracker.
Attackers can target a specific entry point like ``asdxzxc`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "token-usage-tracker GHSA-6fxh-5965-3xf4" on the vendor's site.
GHSA-6fxh-5965-3xf4 (token-usage-tracker) —
Attack surface: `asdxzxc` / `hardhat` / `metamask` / `CLAUDE.md`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in token-usage-tracker. Attackers reach the vulnerable code path via ``asdxzxc`` without authentication.
📍 Affected scope
token-usage-tracker — . Attack surface: `asdxzxc` / `hardhat` / `metamask` / `CLAUDE.md`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'token-usage-tracker' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'token-usage-tracker' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `token-usage-tracker` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
token-usage-tracker
[{"type":"SEMVER","events":[{"introduced":"0"}]}]