Which versions of babyyodaa are malicious?

The following npm versions of babyyodaa are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate babyyodaa if I installed it?

Remove babyyodaa from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed babyyodaa — how do I know if it already compromised me?

If babyyodaa 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.

How do I find babyyodaa across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for babyyodaa (version 1.1.0).

Malicious package

babyyodaanpm

Advisory published Nov 2, 2026Updated Nov 4, 2026

babyyodaa is a confirmed malicious npm package (MAL-2026-18605) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in babyyodaa (npm)

MAL-2026-18605

Immediate action

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

npm uninstall babyyodaa

What this malware does

Runs on install. The preinstall script marks a shell script bundled in the package as executable and runs it; the script contains a reverse-shell pattern, giving a remote party a shell on the installing machine. Version examined: 1.1.0; tarball SHA-256 8321ef8b36b40d9a5b5ba649e9ad4ec3bcbe18a9a484075c5e8e5e872ec0db0b.

Malicious versions

1 flagged

1.1.0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for babyyodaa (version 1.1.0).
If you installed it — respond
Remove babyyodaa from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If babyyodaa 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. babyyodaa on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Oluwatosin Amokeodo · finder

Detect & block this

O3 blocks babyyodaa-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database