What does the mabibilabub malware do?

The package mabibilabub was found to contain malicious code. The OpenSSF Package Analysis project identified 'mabibilabub' @ 1.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of mabibilabub are malicious?

The following npm versions of mabibilabub are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate mabibilabub if I installed it?

Remove mabibilabub 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 mabibilabub — how do I know if it already compromised me?

If mabibilabub 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 mabibilabub across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mabibilabub (version 1.0.0).

Malicious package

mabibilabubnpm

Advisory published Mar 11, 2026Updated Mar 23, 2026

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

Malicious code in mabibilabub (npm)

MAL-2026-1349

Immediate action

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

npm uninstall mabibilabub

What this malware does

The package mabibilabub was found to contain malicious code.

The OpenSSF Package Analysis project identified 'mabibilabub' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

61a1af8f9e6be576e0cc2c70e4c64eaa8376171e26c2bebc2085958f4f8d965d

7b5848598772336361b5ae5218b3379ba6b80420c35d0ef05fcfae6d82688a29

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for mabibilabub (version 1.0.0).
If you installed it — respond
Remove mabibilabub 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 mabibilabub 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. mabibilabub 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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks mabibilabub-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