Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in node-telegram-sockets (npm)

GHSA-c773-2559-g4g3

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm node-telegram-sockets

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (222b22669330f75e779595b40bac9e2a842ef38fad691aaa46a0f4a615a55fc1) Package presents as a Telegram bot API client library (node-telegram-bot-api family). a static rule fired on keyword co-occurrence in lib/telegram.js and src/telegram.js (the literal token 'ping' on multiple lines, consistent with Telegram bot 'ping'-related API methods or test fixtures, not a child_process invocation of the ping command) and on lib/telegramWebHook.js / src/telegramWebHook.js for the combination of require('fs') + require('http') + require('https') + fs.readFileSync — the canonical shape of a webhook HTTPS server reading a TLS cert/key from disk (the readFileSync pair at adjacent lines is the standard cert+key load before https.createServer). No hardcoded attacker C2, no env-var scraping, no read of installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc, browser profiles), no lifecycle scripts performing remote…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-17845

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-c773-2559-g4g3

Advisory: Malicious code in node-telegram-sockets (npm)
IDs: GHSA-c773-2559-g4g3
Record: https://patchnext.com/advisories/mal-2026-17845 (revision 1, source checked 30 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-telegram-sockets: affected every version

## Suggested inspection (read-only)
- `npm ls node-telegram-sockets --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-telegram-sockets.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-17845 (OSV record MAL-2026-17845 lists affected ranges: npm node-telegram-sockets >=0)

Commands are suggestions: review each one before running it.

Loading voting…