---
id: "MAL-2026-19950"
page: "https://infrastack.ai/live/MAL-2026-19950"
kind: "package"
aliases: ["MAL-2026-19950"]
title: "Malicious code in tg-msg-effect (npm)"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "tg-msg-effect", "note": "all versions", "fixed": [], "affected": "", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["malicious", "package"]
not_affected_if: []
published_at: "2026-11-14T15:13:52+00:00"
first_seen_at: "2026-11-16T06:03:37+00:00"
updated_at: "2026-11-16T06:12:20+00:00"
sources: [{"source": "osv-malicious", "url": "https://osv.dev/vulnerability/MAL-2026-19950", "first_seen_at": "2026-11-16T06:03:37+00:00"}]
exploit_sources: []
---

# Malicious code in tg-msg-effect (npm)

Link for people: https://infrastack.ai/live/MAL-2026-19950 (this .md is for agents)

## Affected

- npm:tg-msg-effect affected range not listed fixed no fixed version listed

## Timeline

- 2026-11-16T06:03:37+00:00 osv-malicious https://osv.dev/vulnerability/MAL-2026-19950

## From the sources

`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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
