mal-2026-19950
Vulnerability from ossf_malicious_packages
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.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "tg-msg-effect",
"purl": "pkg:npm/tg-msg-effect"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"1.0.7",
"1.0.8",
"1.0.9",
"1.0.10"
]
}
],
"credits": [
{
"contact": [
"https://x.com/w0rmsign"
],
"name": "wormsign",
"type": "FINDER"
}
],
"database_specific": {
"iocs": {
"urls": [
"https://api.telegram.org/bot8456787917/sendDocument"
]
}
},
"details": "`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, `\u003chex\u003es` 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\u0027s logged-in Telegram sessions.",
"id": "MAL-2026-19950",
"modified": "2026-11-14T15:13:52Z",
"references": [
{
"type": "WEB",
"url": "https://wormsign.io/portfolio/tg-msg-effect/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in tg-msg-effect (npm)"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.