video-core-sdk@1.0.72
Core-SDK 是渲染部分的 SDK,传入工程数据(JSON)可以将数据绘制到 Canvas 上。
AI Security Review
scanned 1mo ago · by lpm-firewall-aiScanner malware fingerprints and obfuscation flags come from a single minified video SDK that also embeds lodash, lottie, PixiJS, and ffmpeg.wasm. There are no install hooks and no harvest, exfil, or hidden loader beyond the documented effect-script import.
Decision evidence
public snapshot- The published JavaScript is one minified line, so scanners flag eval, Function, dynamic require, and malware fingerprints that match bundled lodash, lottie, and PixiJS helpers.
- When movie data includes an effect script name, the SDK injects a script tag from a configurable effect path or the vendor CDN.
- package.json has no preinstall, install, postinstall, bin, or self-dependency fields.
- README and TypeScript types export VideoCoreSDK as a canvas movie renderer, matching the bundled class.
- Network strings are cdn.h5ds.com, ffmpeg wasm paths, PixiJS, and GLSL comment URLs, not a command-and-control host.
- No child_process, env or cookie harvest, webhook, persistence, or reviewer-directed text was found.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
video-core-sdk.jsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
video-core-sdk.jsView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
video-core-sdk.jsView on unpkgFindings
Affected versions and remediation
This report applies to video-core-sdk@1.0.72.
See all versions of video-core-sdk for other recorded verdicts.
- Review the evidence and your use of video-core-sdk@1.0.72 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.