tilaver-mfa
tilaver-mfa-app
This report shows the evidence for tilaver-mfa@1.0.0. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms credential collection and exfiltration, not merely suspicious primitives. The lack of an install lifecycle hook limits the trigger to import/execution but does not make the payload benign.
Decision evidence
public snapshot- `index.js` executes `run()` at top level.
- `index.js` reads APPDATA, LOCALAPPDATA, and the home directory.
- `index.js` defines Discord token patterns and AES-GCM decryption.
- `index.js` collects `discord`, `passwords`, `cookies`, `roblox`, `cards`, and `screenshot` data.
- `index.js` embeds a Discord webhook and POST relay to `150.136.37.62:5000/api/v2/c`.
- `index.js` uses `child_process.execSync`, filesystem access, and worker-thread relay code.
- `package.json` contains no preinstall, install, or postinstall lifecycle hook.
- Only `package.json` and the obfuscated `index.js` are present; no legitimate MFA implementation is evident.
Source & flagged code
7 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
index.jsView on unpkg · L1A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to tilaver-mfa@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing tilaver-mfa@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.