Malicious code in fazzgram (npm)
Source: amazon-inspector
fazzgram is a Telegram Bot API wrapper. Supporting modules (ApiClient.js, Dispatcher.js, LongPoller.js, WebhookServer.js, Context.js, Markup.js) are plain, readable code that only POSTs to api.telegram.org using the caller-supplied bot token; there are no install lifecycle scripts, no environment-variable scraping, no reads of credential paths, no child_process usage, and no third-party network destinations. However, src/FazzGram.js and src/methods/index.js are wrapped in a custom JS-VM interpreter (base64-encoded bytecode array plus dispatch loop) with an anti-debug timing trap that triggers debugger and calls _setDeceptionDetected() when process.hrtime.bigint() indicates a debugger is attached. The wrapped logic appears to be trivial pass-through method dispatch to api.telegram.org — a use case with no legitimate need for bytecode-VM obfuscation. Decoded bytecode strings reference only telegram.org endpoints and no exfiltration, dropper, or credential-access behavior is observable, but the combination of heavy obfuscation, anti-debug instrumentation, placeholder author, and a fresh v0.1.0 publish is the structural shape used to stage payloads in later versions and warrants human review before installer use.
Source: ghsa-malware
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
