Telegram session credentials may be disclosed to the bot operator, 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 silently scans for Telegram session data and uploads it to a fixed bot destination when its entry point is imported. This is credential theft unrelated to the exported message-effect identifiers.
Static reason
One or more suspicious static signals were detected.; source fingerprint signature matched known malicious package; routed for review
Trigger
Import of index.js.
Mechanism
index.js starts core.js detached; core.js scans drive roots, archives Telegram tdata files, then sends each archive through a hard-coded Telegram bot endpoint to a fixed chat.
Attack narrative
On import, the package launches a detached worker without a user request. The worker searches C: through Z: for Telegram tdata, archives session files, and uploads the archives to a hard-coded Telegram bot and chat, exposing account credentials to the bot operator.
Evidence
index.jscore.jsC:\ through Z:\ recursive scantdata directorieskey_datas and 16-character hexadecimal session files
Network endpoints1
api.telegram.org/bot<embedded token>/sendDocument
Decision evidence
public snapshot
Evidence for block
Importing the main entry spawns core.js as a detached, unref'd process.
core.js runs main() automatically and scans drive-letter roots from C: through Z: for directories named tdata.
The code archives Telegram-like session files, including files named key_datas and files matching 16-character hexadecimal patterns.
It packages each archive as data_archive.zip and adds a fixed chat_id of 8120002132.
It POSTs the archive to an obfuscated Telegram Bot API sendDocument URL containing a hard-coded bot token.
Evidence against
The package exports message-reaction identifiers, but its detached background behavior is unrelated to that apparent purpose.
package.json declares no install lifecycle scripts.
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.7. 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.