Which versions of @astralcore/aura-wb are malicious?

The following npm versions of @astralcore/aura-wb are flagged malicious: 1.0.0, 1.0.1, 1.0.4. Treat any of these as compromised.

How do I remediate @astralcore/aura-wb if I installed it?

@astralcore/aura-wb 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 @astralcore/aura-wb — how do I know if it already compromised me?

If @astralcore/aura-wb was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @astralcore/aura-wb part of a known attack campaign?

Yes — @astralcore/aura-wb is associated with the IN-MAL-2026-016498, IN-MAL-2026-016502, IN-MAL-2026-016503 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 @astralcore/aura-wb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @astralcore/aura-wb (3 malicious versions).

Malicious package

@astralcore/aura-wbnpm

Advisory published Aug 6, 2026Updated Aug 6, 2026

@astralcore/aura-wb is a confirmed malicious npm package (MAL-2026-13413) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @astralcore/aura-wb (npm)

MAL-2026-13413

Immediate action

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

npm uninstall @astralcore/aura-wb

What this malware does

The package is a WhatsApp (Baileys) bot whose default configuration in config/index.js points MONGODB_URI at a hardcoded shared Atlas cluster (mongodb+srv://unity-free:[email protected]) with credentials embedded in the source. When an installer starts the bot without overriding MONGODB_URI, useMongoDBAuthState() in src/commands/index.js writes the full Baileys creds and signal keys — the noise key, signal identity key, registration, and session keys that grant complete control of the installer's WhatsApp account — to that author-controlled database. src/commands/boostWatcher.js opens on 'connection open' and polls the same shared MongoDB every 20 seconds for BoostJob documents, then drives followNewsletter, newsletterReactMessage, and readMessages against the installer's paired WhatsApp session for each job. Because the DB credentials are shared and hardcoded, anyone with the source (including the author) can read every installer's WhatsApp session material and enqueue jobs that command every installer's WhatsApp identity to follow, react to, or view arbitrary channels. Additional install-time and command paths in start.js, src/commands/boost.js, and src/telegram/notify.js post host information (os.platform, os.arch, process.env) to api.telegram.org/bot<redacted>/sendMessage using a hardcoded owner chat_id 7752365037, providing the author install-time notifications on every deployment. A Google Tenor API key is also embedded in src/commands/extra_media.js.

Malicious versions

3 flagged

1.0.01.0.11.0.4

Indicators of compromise (SHA-256)

2bcf5586718d048bf142fce2aba00c5823cadf0d4bbf7d015a780c8714dc4ac5

7cf8d2997880a86b08dbe855f09955c3b760e7098710d1775ce588f25af5ee95

bd4a1b22725e981c18c44de0f81915a5048b58bdcacfe6935c9dfcb3dceb641c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @astralcore/aura-wb (3 malicious versions).
If you installed it — respond
@astralcore/aura-wb 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 @astralcore/aura-wb was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @astralcore/aura-wb on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016498IN-MAL-2026-016502IN-MAL-2026-016503

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @astralcore/aura-wb-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