Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2017-16126 — botbait

MEDIUM

CVE-2017-16126 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in botbait. No vendor fix is recorded yet; mitigation options are listed below.

Tracking Module in botbait

Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-16126 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

botbaitnpm
4downloads / week

Description

The module botbait is a tool to be used to track bot and automated tools usage with-in the npm ecosystem.

botbait is known to record and track user information.

The module tracks the following information.

  • Source IP
  • process.versions
  • process.platform
  • How the module was invoked (test, require, pre-install)

Recommendation

This package has no functional value, and should be removed from your environment if discovered.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmbotbait≥ 0.0.0No fix

Affected Products

1 product · 1 configurations
Application
botbaitbotbait_project
≤ 2.0.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for botbait, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of botbait has shipped for CVE-2017-16126 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

The module `botbait` is a tool to be used to track bot and automated tools usage with-in the npm ecosystem. `botbait` is known to record and track user information. The module tracks the following information. - Source IP - process.versions - process.platform - How the module was invoked (test, require, pre-install) ## Recommendation This package has no functional value, and should be removed from your environment if discovered.
O3 Security · Impact-Aware SCA

Is CVE-2017-16126 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-16126: botbait: Tracking Module