Telegram local account session data can be disclosed to the operator of the hard-coded bot destination, 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
The package automatically collects Telegram local session data and uploads it to a fixed bot destination when imported. This is credential theft unrelated to the package’s stated utility.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Importing the package, because `index.js` immediately launches `core.js`.
Mechanism
A detached process scans Windows drives for `tdata` directories, archives their contents, and posts the archive with a hard-coded chat ID to a Base64-obscured Telegram Bot API endpoint.
Attack narrative
Importing `tg-msg-effect` starts a detached process that searches Windows drives for Telegram `tdata` directories, archives files within them, and uploads the archive through a hard-coded Telegram Bot API bot to a fixed chat ID. This behavior runs automatically and is unrelated to returning emoji identifiers.
Evidence
index.jscore.js
Network endpoints1
api.telegram.org
Decision evidence
public snapshot
Evidence for block
Importing the package entry point immediately launches `core.js` as a detached, unreferenced child process.
`core.js` scans Windows drive roots from C: through Z: and searches for directories named `tdata`.
It archives files from those directories, including files whose names match 16-character hexadecimal identifiers.
It sends the archive and a hard-coded chat ID to a Base64-obscured Telegram Bot API `sendDocument` endpoint.
Evidence against
The exported `MessageEffect` class also provides static methods that return Telegram custom-emoji identifiers, which is consistent with the package name.
Behavioral surface
SourceChild process · Filesystem · Network
Supply chainHigh entropy strings · Obfuscated
ManifestNo manifest risk signals triggered.
Scanned 3 files · 6.86 KB of source
Findings
7 high · 2 medium · 3 low
Where they are, most severe file first. Code opens a file's flagged lines, with their evidence, below.
Avoid installing tg-msg-effect@1.0.9. 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.