spark-sf
single file for my website
This report shows the evidence for spark-sf@1.0.2. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete remote code execution path in the package's exported runtime artifact, with no integrity control over the downloaded JavaScript. The absence of an npm lifecycle hook does not remove the runtime attack surface.
Decision evidence
public snapshot- The default export is an SVG runtime artifact.
- The browser code fetches JavaScript from bestspark.org, base64-wraps it as a data URL, and dynamically imports it.
- It replaces window.fetch and forwards requests through a WebSocket service.
- The shipped SVG contains the generated browser application; its build helper inlines the classic script into it.
- No npm install lifecycle hook is present.
- No local credential or filesystem harvesting was confirmed.
Source & flagged code
6 flagged · loading sourceSource fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
single.jsView on unpkg · L117Package source references dynamic require/import behavior.
single.jsView on unpkg · L6495Findings
Affected versions and remediation
This report applies to spark-sf@1.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing spark-sf@1.0.2. 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.