parxleys
WhatsApp Web API Library
This report shows the evidence for parxleys@1.0.1. 2 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource proves automatic, remotely directed account manipulation through the active socket entrypoint. The benign lifecycle and media-processing findings do not explain or neutralize this behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A WhatsApp connection opens, followed by a 30-second timer.
Impact
Changes the user's channel subscriptions and notification settings without an explicit request.
Mechanism
Fetch a remote JSON channel list and issue authenticated FOLLOW and MUTE queries for its entries.
Attack narrative
Creating the normal socket registers a connection listener. After the connection opens, the listener fetches an external channel list and uses the authenticated socket to follow and mute those channels. Remote list changes can therefore determine unsolicited account subscriptions without a separate user command.
AI rationale
Source proves automatic, remotely directed account manipulation through the active socket entrypoint. The benign lifecycle and media-processing findings do not explain or neutralize this behavior.
Evidence
lib/index.jslib/Socket/index.jslib/Socket/business.jslib/Socket/messages-recv.jslib/Socket/messages-send.jslib/Socket/newsletter.js
Network endpoints1
raw.githubusercontent.com/noxXza/data/refs/heads/main/noxleys.json
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The exported makeWASocket entrypoint reaches the newsletter socket through the business and message socket layers.
- The newsletter socket fetches channel identifiers from a fixed GitHub URL controlled outside the user's account.
- For each accepted channel identifier, the code sends FOLLOW and then MUTE requests using the connected account.
- A connection-open event automatically starts this behavior after 30 seconds, without an opt-in check.
Evidence against
- The preinstall hook only checks the Node.js version; prepare prints a message.
- The flagged eval imports a fixed audio decoder, and FFmpeg is used for thumbnail generation.
Behavioral surface
ChildProcessCryptoEvalFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.preinstall = node ./engine-requirements.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkglib/WABinary/constants.jsView file
603patternName = google_api_key
severity = high
line = 603
High
High Secret
Package contains a high-severity secret pattern.
lib/WABinary/constants.jsView on unpkg · L603603patternName = google_api_key
severity = high
line = 603
High
Secret Pattern
Google API key in lib/WABinary/constants.js
lib/WABinary/constants.jsView on unpkg · L603lib/Utils/messages-media.js
Findings
4 High3 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighHigh Secretlib/WABinary/constants.js
HighSemantic Analysis LimitedWAProto/index.js
HighSecret Patternlib/WABinary/constants.js
MediumNetwork
MediumOversized Source FileWAProto/index.js
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvallib/Utils/messages-media.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to parxleys@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing parxleys@1.0.1. 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.