tg-msg-effectnpm
Advisory published Updated
tg-msg-effect is a confirmed malicious npm package (MAL-2026-19950) that executes malicious code on install (malicious versions 1.0.7, 1.0.8, 1.0.9…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tg-msg-effect (npm)
What this malware does
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.
Malicious versions
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for tg-msg-effect (4 malicious versions).
If you installed it — respond
Remove tg-msg-effect from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tg-msg-effect was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
References
Credits
- wormsign · finder
Detect & block this
O3 blocks tg-msg-effect-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.