react-flying-reaction
React flying reaction
This report shows the evidence for react-flying-reaction@3.0.1. 2 of 4 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe component contains a concrete, destructive action against the consuming application's DOM, guarded only by remote-controlled license status. No install hook is needed for this harmful runtime behavior.
Decision evidence
public snapshot- The obfuscated component replaces the consumer page body with a new empty body after a failed license check outside localhost.
- Mounting the component automatically verifies a license and can fetch a remote revocation list.
- The published entry point is deliberately obfuscated, concealing this destructive browser behavior.
- package.json has no install lifecycle scripts and declares only React as a peer dependency.
- The inspected code contains no child-process, shell, filesystem, or credential-exfiltration behavior.
Source & flagged code
4 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
index.jsView on unpkg · L1The obfuscated component replaces the consumer page body with a new empty body after a failed license check outside localhost.
index.jsView on unpkg · L1Mounting the component automatically verifies a license and can fetch a remote revocation list.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to react-flying-reaction@3.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing react-flying-reaction@3.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.