tg-msg-effect

Ecosystem: npm

Downloads:

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 0HighAffects 0 versions
  • 0MediumAffects 0 versions
  • 0ModerateAffects 0 versions
  • 0LowAffects 0 versions
Severity distribution (all time)
0vulnerabilities
  • Critical0 (0.0%)
  • High0 (0.0%)
  • Medium0 (0.0%)
  • Moderate0 (0.0%)
  • Low0 (0.0%)

Monthly breakdown

  • 0 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 0
    • Low: 0

Vulnerabilities (1)

Known vulnerabilities affecting tg-msg-effect, based on data from OSV.

Vulnerabilities affecting tg-msg-effect
IDSeveritySummaryAffected versionsPublishedSource
MAL-2026-19950UnknownMalicious code in tg-msg-effect (npm)`tg-msg-effect` poses as a Telegram message-effect helper. On import, `index.js` starts a detached, silenced `node core.js`. On Windows, `core.js` walks drives C: to Z:, collects every Telegram Desktop `tdata` session folder (the 16-hex session files, `<hex>s` directories and `key_datas`), zips them into `data_archive.zip` and uploads it to a base64-encoded, hardcoded Telegram bot (bot8456787917, chat 8120002132) via `sendDocument`. This hands the publisher the victim's logged-in Telegram sessions.
  • all
OSV (opens in a new tab)
  • MAL-2026-19950Unknown
    Malicious code in tg-msg-effect (npm)
    • all

    `tg-msg-effect` poses as a Telegram message-effect helper. On import, `index.js` starts a detached, silenced `node core.js`. On Windows, `core.js` walks drives C: to Z:, collects every Telegram Desktop `tdata` session folder (the 16-hex session files, `<hex>s` directories and `key_datas`), zips them into `data_archive.zip` and uploads it to a base64-encoded, hardcoded Telegram bot (bot8456787917, chat 8120002132) via `sendDocument`. This hands the publisher the victim's logged-in Telegram sessions.

Showing 1-1 of 1 vulnerabilities