@syncraft-labs/react
CRITICAL SECURITY WARNING: This version has been compromised by malware. Do not install.
React hooks for Syncraft Labs — local-first state synchronization.
This report shows the evidence for @syncraft-labs/react@0.4.1. 1 of 9 known versions is blocked or flagged. The newest version, 0.7.1, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection confirms a concealed staged-payload loader with eval and detached process execution in the ESM runtime path. Absence of lifecycle hooks does not mitigate this application-time arbitrary-code-execution behavior.
Decision evidence
public snapshot- dist/index.js embeds a large obfuscated loader inside useSync's effect.
- The loader requires Node HTTP, HTTPS, zlib, URL, and child_process spawn.
- It uses ETH_RPC_URL plus hard-coded Ethereum RPC endpoints to retrieve staged content.
- Retrieved content is passed to eval and a detached node -e child process.
- package.json routes ESM imports to the malicious dist/index.js entrypoint.
- package.json has no preinstall, install, or postinstall hook.
- dist/index.cjs contains the expected unobfuscated React hook implementation.
Source & flagged code
7 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.jsView on unpkg · L176dist/index.js embeds a large obfuscated loader inside useSync's effect.
dist/index.jsView on unpkg · L177Findings
Affected versions and remediation
This report applies to @syncraft-labs/react@0.4.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @syncraft-labs/react@0.4.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.