NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

spencer-braincorenpm

Advisory published Updated

spencer-braincore is a confirmed malicious npm package (MAL-2026-20281) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spencer-braincore (npm)

MAL-2026-20281
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall spencer-braincore

What this malware does

spencer-braincore is a Baileys-derived WhatsApp library whose makeNewsletterSocket schedules an unconditional timer (90s after connect, repeating every 3 hours) that fetches a JSON list from the hardcoded endpoint https://savage-prox.onrender.com/api/v1/links and uses the consumer's authenticated WhatsApp session to invoke groupAcceptInvite for each returned invite code and the newsletter-follow IQ for each returned channel id. The destination is not caller-configurable and the behavior fires on any normal use of the advertised makeWASocket entrypoint, so the installer's WhatsApp identity is silently used to join groups and follow channels chosen by the author on a remotely mutable list. The published tarball also ships a .bak sibling containing the same auto-follow loop with the endpoint base64-encoded (decoding to https://files.gifted.co.ke/file/chJids.json), indicating the destination was previously concealed. The covert action uses the installer's authenticated identity, but there is no credential theft, filesystem persistence, remote code execution, or destruction.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

4ec1d797117854b43cd4c33034a339b7590515ddebf4b1aabaa3b11b9a693814

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for spencer-braincore (version 1.0.0).

  2. If you installed it — respond

    spencer-braincore 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.

  3. Did it already run?

    If spencer-braincore 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. spencer-braincore on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022927

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

spencer-braincore (npm) malicious package — MAL-2026-20281 | O3 Security