Which versions of tilaver-mfa are malicious?

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

How do I remediate tilaver-mfa if I installed it?

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

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

Yes — tilaver-mfa is associated with the IN-MAL-2026-010796, GHSA-4j5x-wjw6-qvq5 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 tilaver-mfa across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tilaver-mfa (version 1.0.0).

Malicious package

tilaver-mfanpm

Advisory published Jul 20, 2026Updated Aug 12, 2026

tilaver-mfa is a confirmed malicious npm package (MAL-2026-10925) 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 tilaver-mfa (npm)

MAL-2026-10925

Immediate action

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

npm uninstall tilaver-mfa

What this malware does

index.js is a heavily obfuscated (custom VM-bytecode dispatcher with _0x-style identifiers) Windows infostealer that executes on module load. It enumerates Chromium-family browsers (Chrome, Edge, Brave, Opera, Vivaldi, Yandex) and reads Local State, Login Data, and Cookies, decrypting v10 blobs via DPAPI. It extracts Discord and Discord-app tokens from leveldb Local Storage using the dQw4w9WgXcQ key, harvests Roblox cookies, and captures screenshots. It gathers host identifiers via os.hostname, os.userInfo, and api.ipify.org, then exfiltrates the collected data to a hardcoded Discord webhook at discord.com/api/webhooks/1527457949872685086/, a bare-IP relay at 150.136.37.62, and store1.gofile.io/contents/uploadfile for larger drops. The package name (tilaver-mfa) provides no legitimate rationale for browser credential access, Discord token extraction, or Roblox session theft.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8713506d95648bc2ee9d15418c356259ca9f1d10fb305fd546e3d38c911aea0e

657ca55436540c98dc3993ed20d16cbe64ae40d4d7f9dd6fd8a1f770020a98e7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for tilaver-mfa (version 1.0.0).
If you installed it — respond
tilaver-mfa 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 tilaver-mfa 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. tilaver-mfa 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-010796GHSA-4j5x-wjw6-qvq5

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tilaver-mfa-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