Which versions of hridoy-ultimate are malicious?

The following npm versions of hridoy-ultimate are flagged malicious: 8.0.0. Treat any of these as compromised.

How do I remediate hridoy-ultimate if I installed it?

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

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

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

Search your lockfiles and build artifacts for hridoy-ultimate (version 8.0.0).

Malicious package

hridoy-ultimatenpm

Advisory published Oct 11, 2026Updated Oct 11, 2026

hridoy-ultimate is a confirmed malicious npm package (MAL-2026-17803) that steals credentials and exfiltrates sensitive data (malicious version 8.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hridoy-ultimate (npm)

MAL-2026-17803

Immediate action

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

npm uninstall hridoy-ultimate

What this malware does

hridoy-ultimate 8.0.0 is an unofficial Facebook chat client that contains two installer-harming behaviors. First, the password-based login path in module/loginHelper.js forwards caller-supplied Facebook email, password, and Base32 TOTP 2FA secret to a hardcoded third-party endpoint at https://minhdong.site/api/v1/facebook/login_ios (default baked into module/config.js, not disclosed in README) and receives the resulting Facebook session cookies / access_token back through that server, giving the operator of minhdong.site full access to any account whose credentials pass through this path. Second, package.json declares fca-unofficial as github:VangBanLaNhat/fca-unofficial with no commit SHA or tag; npm resolves this against whatever the referenced repository's default branch contains at install time, and the vendor bundle under src/api/socket/e2ee/ actually requires that module, so arbitrary code controlled by that GitHub repo owner is pulled and executed on the installer at install and load time with no integrity check and no version lock. A separate opt-in WebSocket remote-control client (src/remote/remoteClient.js) is config-gated and does not itself exec received data.

Malicious versions

1 flagged

8.0.0

Indicators of compromise (SHA-256)

221c8e51e1341e954c4f2ea3ea4a139606138c8ecc1ab99e17f403e304f05157

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hridoy-ultimate (version 8.0.0).
If you installed it — respond
hridoy-ultimate 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 hridoy-ultimate 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. hridoy-ultimate on npm has been identified as a malicious package (version 8.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021451

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hridoy-ultimate-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