@divineubg/divine
This report shows the evidence for @divineubg/divine@1.1.2. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe code contains an automatic remote command channel whose EVAL_CODE action directly executes attacker-supplied JavaScript. The lack of an npm lifecycle hook does not mitigate this concrete runtime remote-code-execution behavior.
Decision evidence
public snapshot- On first browser use, the package opens an ntfy command stream tied to a generated client ID.
- Messages requesting EVAL_CODE are executed with eval or Function, allowing the remote sender to run arbitrary browser JavaScript.
- The package also decodes remotely fetched game assets and writes the resulting code into a script-enabled iframe.
- The manifest exposes index.js as the entry point, and the browser page loads it automatically.
- package.json contains no preinstall, install, or postinstall hook.
- No Node child-process, filesystem harvesting, or environment-variable access appears in the inspected source.
Source & flagged code
6 flagged · loading sourceSource passes code obtained from a remote response into a dynamic execution sink.
index.jsView on unpkg · L1On first browser use, the package opens an ntfy command stream tied to a generated client ID.
Findings
Affected versions and remediation
This report applies to @divineubg/divine@1.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @divineubg/divine@1.1.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.