Malicious code in discord-resolvers (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (6aa01ed90340a9458c2906ec74fd9277bb7d0e4da48ef09487639aa6c45e6791) The package published as discord-resolvers is unrelated to Discord. On require, index.js invokes startBackupLoop() at top level, which recursively archives the /root directory on Linux (or the drive root, typically C:\, on Windows) into a ZIP and uploads it via the Telegram Bot API to a hardcoded chat controlled by the package author. The loop repeats every hour and all errors are silently swallowed. The exclude list (node_modules,.git,.cache, tmp) does not exclude credential-bearing paths such as ~/.ssh, ~/.aws, ~/.npmrc,.env files, browser profiles, or wallet stores, so SSH keys, cloud credentials, source code, and other secrets under the archived root are shipped off-host. The Telegram bot token (8296271388:AAH-...) and chatId (8851479019) ship in cleartext in config.json and are the transport mechanism for the exfiltration; the destination is not caller-configurable. The package.json description ("Cross-platform automated server backup tool with Telegram delivery") self-labels the behavior but the package name and the silent auto-execution on require make this a covert exfiltration payload rather than an opt-in backup tool. ## Source: ghsa-malware (55190e72768fe3097d180a9ab559f286193f109b0aea457a90e02dc405458ad5) 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.

Source published

16 Sep 2026 06:37:31 UTC

Source modified

28 Sep 2026 04:45:05 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.