Malicious code in @astralcore/aura-wb (npm)
The npm package @astralcore/aura-wb contains malicious code that exfiltrates WhatsApp session credentials (Baileys creds and signal keys) to an attacker-controlled MongoDB cluster and enables remote command execution against paired WhatsApp accounts via a shared database polling mechanism.
- Disclosed
- Last updated
- Blast radius
- All installers of affected versions who did not override the hardcoded MongoDB URI; WhatsApp account credentials and session keys exposed to attacker-controlled database; arbitrary commands executable against paired WhatsApp sessions.
- Ecosystems
- Attack vectors
- Affected entities
- @astralcore/aura-wbWhatsApp bot package with hardcoded credentials and malicious data exfiltration
@astralcore/aura-wb is a WhatsApp bot package that contains hardcoded credentials and malicious functionality designed to compromise user WhatsApp accounts. The package's default configuration points to a shared MongoDB Atlas cluster (mongodb+srv://unity-free:unity-free@unity-free.pc6vkvw.mongodb.net) with embedded credentials in the source code.\n\nWhen installers run the bot without overriding the MONGODB_URI environment variable, the package writes complete WhatsApp session material to the attacker-controlled database. This includes Baileys credentials, noise keys, signal identity keys, registration keys, and session keys that grant full control of the paired WhatsApp account.\n\nThe package implements a command-and-control mechanism via src/commands/boostWatcher.js that polls the shared MongoDB every 20 seconds for BoostJob documents. These jobs allow the attacker to execute arbitrary actions on the installer's WhatsApp session, including following channels, reacting to messages, and reading messages. Because the database credentials are hardcoded and shared, any party with access to the source code can read all installer credentials and enqueue malicious jobs.\n\nAdditionally, the package exfiltrates host information (OS platform, architecture, environment variables) to a hardcoded Telegram chat ID via api.telegram.org during installation and command execution, further compromising installer privacy and security.
Indicators of compromise
- Packages
- @astralcore/aura-wb
- Domains
- api.telegram.org
Remediation
- Immediately uninstall @astralcore/aura-wb from all systems
- If the package was installed and run, assume the paired WhatsApp account is compromised; change WhatsApp password and review account activity
- Revoke any API tokens or credentials that may have been exposed via environment variables
- Audit npm package dependencies for similar malicious patterns
- Report the package to npm security for removal from the registry
- Monitor paired WhatsApp accounts for unauthorized activity
Sources
- GitHub Advisory GHSA-5hgw-c6cc-2g2x · GitHub Advisory Database
Cite this entry
"Malicious code in @astralcore/aura-wb (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 6, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-astralcore-aura-wb-npm-1sax7s
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package