Which versions of discord-resolvers are malicious?

The following npm versions of discord-resolvers are flagged malicious: 3.4.2. Treat any of these as compromised.

How do I remediate discord-resolvers if I installed it?

discord-resolvers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed discord-resolvers — how do I know if it already compromised me?

If discord-resolvers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is discord-resolvers part of a known attack campaign?

Yes — discord-resolvers is associated with the IN-MAL-2026-020091 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find discord-resolvers across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for discord-resolvers (version 3.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discord-resolvers across your stack and pipelines.

Malicious package

discord-resolversnpm

discord-resolvers is a confirmed malicious npm package (MAL-2026-16214) that steals credentials and exfiltrates sensitive data (malicious version 3.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in discord-resolvers (npm)

MAL-2026-16214

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall discord-resolvers

What this malware does

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.

Malicious versions

1 flagged

3.4.2

Indicators of compromise (SHA-256)

6aa01ed90340a9458c2906ec74fd9277bb7d0e4da48ef09487639aa6c45e6791

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for discord-resolvers (version 3.4.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discord-resolvers across your stack and pipelines.
If you installed it — respond
discord-resolvers is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If discord-resolvers was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks discord-resolvers before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. discord-resolvers on npm has been identified as a malicious package (version 3.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020091

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks discord-resolvers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database