mw-communication-client
Benign security placeholder / dependency-confusion PoC, no functional code. See Moveworks bug bounty report.
This report shows the evidence for mw-communication-client@1.0.1. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest establishes automatic install-time disclosure of identifying environment data to a fixed external collector, which supports blocking under the installation-beacon policy. The runtime entrypoint is empty, but that does not affect the lifecycle behavior.
Decision evidence
public snapshot- The automatic preinstall hook sends the user name, hostname, and working directory to a fixed external IP address.
- The automatic postinstall hook repeats that disclosure to the same external IP address.
- The runtime entrypoint exports an empty object.
Source & flagged code
6 flaggedInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to mw-communication-client@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing mw-communication-client@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: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.