Telegram session data is sent to a publisher-controlled bot and chat, potentially enabling account access.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
Importing the package starts an obfuscated background worker that searches for Telegram session data and uploads it to a hard-coded Telegram bot. This is credential theft unrelated to the exported reaction identifiers.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Importing the package entry point index.js.
Mechanism
index.js starts core.js in a detached process. The worker scans Windows drives for Telegram tdata directories, archives session-related files, and uploads each archive through a hard-coded Telegram bot endpoint.
Attack narrative
Importing the package silently starts a detached worker. It searches Windows drives for Telegram Desktop tdata directories, archives session-related files, and sends the archives as documents to a hard-coded Telegram bot and chat. The destination URL is Base64-obscured in source. This exfiltrates Telegram session data without user consent.
Avoid installing tg-msg-effect@1.0.8. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.