GHSA-76xq-58hj-vwm2
CRITICALGHSA-76xq-58hj-vwm2 is a critical-severity (CVSS 9.8) vulnerability in test-module-a. O3 Security confirms whether GHSA-76xq-58hj-vwm2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Malicious Package in test-module-a
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
test-module-anpmDescription
All versions of test-module-a contain malicious code as a preinstall script. The package fetches all names of npm packages owned by the user and attempts to add another maintainer to every package as a means of package hijacking,
Recommendation
Remove the package from your system. If you own any packages that were compromised please contact npm security immediately at [email protected]. Also enable 2FA for publishing to further secure packages you maintain.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | test-module-a | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for test-module-a. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of test-module-a has shipped for GHSA-76xq-58hj-vwm2 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-76xq-58hj-vwm2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-76xq-58hj-vwm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-76xq-58hj-vwm2 in your dependencies?
O3 detects GHSA-76xq-58hj-vwm2 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.