Which versions of nizzybase32 are malicious?

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

How do I remediate nizzybase32 if I installed it?

nizzybase32 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If nizzybase32 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 nizzybase32 part of a known attack campaign?

Yes — nizzybase32 is associated with the IN-MAL-2026-007494 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 nizzybase32 across my projects, lockfiles, and CI pipelines?

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

Malicious package

nizzybase32npm

Advisory published Jun 25, 2026Updated Jun 25, 2026

nizzybase32 is a confirmed malicious npm package (MAL-2026-6450) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nizzybase32 (npm)

MAL-2026-6450

Immediate action

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

npm uninstall nizzybase32

What this malware does

The CLI in bin/hibase32.js computes SHA256 of user input and, on one hardcoded magic digest ('bb9d5bbbd62fc66b63c0866b12656fd9038441acb4f90c136c5a3601e7909a23'), dynamically requires the 'portloop' module and calls portloop.daemon() with ssh=true, sshPort=2223, respawn=true, a hardcoded ngrok auth token ('3EtzBMQ5QHnjZfKJb7roqPKMCqr_3C3Sfc8xevQ7YkokViAHn'), GitHub username 'yazcaleb' as the authorized-keys source, and an embedded ssh-ed25519 public key. The result is a persistent SSH daemon on the installer's host, exposed via an author-controlled ngrok tunnel and authorized only to the author's keys — a hidden remote-shell backdoor. The README advertises 'zero-dependency base32 encoder/decoder', while package.json actually declares 'portloop' as a runtime dependency that is reached only from the backdoor branch, concealing the behavior from anyone reading the documentation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cd8ad52e73a1c796a1dbe22501f4ef2d42f3ceea98cc259e1ceefb1a214cfa56

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for nizzybase32 (version 1.0.0).
If you installed it — respond
nizzybase32 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If nizzybase32 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. nizzybase32 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-007494

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nizzybase32-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database