The recipient may obtain Telegram session data and gain access to affected accounts.
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
The package exfiltrates Telegram session data automatically when its entry point is imported. The detached scanner and hard-coded upload destination are unrelated to the message-effect identifiers the package exports.
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.
Mechanism
index.js starts a detached core.js process. The child scans Windows drives, archives selected Telegram session files, and posts the archive to a hard-coded Telegram bot endpoint and chat ID.
Attack narrative
Importing the package starts a detached process that scans Windows drives for Telegram tdata directories, archives session-related files, and uploads the archive to a hard-coded Telegram bot endpoint and chat ID. This can expose Telegram sessions and enable account access.
Avoid installing tg-msg-effect@1.0.10. 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.