Which versions of toru-ultimate are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for toru-ultimate (version 1.0.0).

Malicious package

toru-ultimatenpm

Advisory published Sep 8, 2026Updated Sep 9, 2026

toru-ultimate is a confirmed malicious npm package (MAL-2026-16057) 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 toru-ultimate (npm)

MAL-2026-16057

Immediate action

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

npm uninstall toru-ultimate

What this malware does

The package's loginViaAPI() function POSTs caller-supplied Facebook email, password, and 2FA Base32 secret to https://minhdong.site/api/v1/facebook/login_ios (a domain unrelated to Facebook, tied to the package's contributor). The response returns Facebook cookies/access_token which are then installed into the caller's session. The README documents login via appState cookies and does not disclose that email/password logins are proxied through minhdong.site. Additionally, package.json declares 'fca-unofficial' as 'github:VangBanLaNhat/fca-unofficial' — an unpinned mutable GitHub reference with no commit SHA. npm install fetches whatever bytes the branch HEAD returns, with no integrity check, and this module is require'd by the bundled E2EE client, so its code runs at import. Whoever controls that GitHub branch controls code delivered to every installer.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e6ef8cb6f3ca866b67fa91f2e770c674ddb7d6b110fd671ba98669dc1220510f

Detection & response playbook

Credential / info stealer

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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