rwc-client
This report shows the evidence for rwc-client@0.29.19. 10 of 10 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms a concrete install-time bootstrapper for an obfuscated credential-harvesting/exfiltration payload. This is malicious behavior, not a package-aligned build dependency.
Decision evidence
public snapshot- package.json runs `node setup.mjs` as preinstall.
- setup.mjs downloads Bun from GitHub and executes math_init.js during install.
- math_init.js is a 728 KB obfuscated executable payload, not chat-client code.
- math_init.js imports child_process, fs, os, and contains credential-token handlers (`ghtoken`, `ghs_old`, `ghs_jwt`).
- The payload enumerates credential candidates and sends data in HTTP POST chunks via fetch.
- Install errors are caught and suppressed after payload execution.
- The runtime dist bundle appears to be a OneReach Vue chat client.
- No AI-agent control-surface mutation was identified.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references a known benign dynamic code generation pattern.
math_init.jsView on unpkg · L1Source contains bidi control or invisible Unicode characters associated with Trojan Source attacks.
dist/lib/richWebChat.umd.min.jsView on unpkg · L312A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/lib/richWebChat.umd.min.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
dist/lib/richWebChat.umd.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
setup.mjsView on unpkgSource fingerprint signature matches a known malicious package signature; route for source-aware review.
setup.mjsView on unpkgFindings
Affected versions and remediation
This report applies to rwc-client@0.29.19.
The versions list below shows the verdict for each recorded version.
- Avoid installing rwc-client@0.29.19. 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.