supersignaturenature
JavaScript library for interacting with the Theta Blockchain
This report shows the evidence for supersignaturenature@1.0.6. 2 of 3 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete import-time execution of decrypted staged code from another package path, not a normal blockchain-library function. The absence of lifecycle hooks does not mitigate the entrypoint-triggered arbitrary code execution.
Decision evidence
public snapshot- The default CommonJS entrypoint runs a detached Node child process during import.
- It reads an encrypted file from a separate tchain-api package, decrypts it, and sends the result to the child process as executable JavaScript.
- The child process has ignored output streams and is unreferenced, concealing execution from the importing application.
- package.json defines no npm lifecycle hook.
- No network endpoint is directly present in the inspected execution block.
Source & flagged code
6 flagged · loading sourceSource spawns a local helper that fetches and dynamically executes remote code.
dist/supersignaturenature.esm.jsView on unpkg · L10Source decodes numeric character arrays into a child-process package-runner command and executes it.
dist/supersignaturenature.esm.jsView on unpkg · L1091Package source references child process execution.
dist/supersignaturenature.esm.jsView on unpkg · L10Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/supersignaturenature.esm.jsView on unpkgA package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/supersignaturenature.cjs.jsView on unpkg · L18Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/supersignaturenature.cjs.jsView on unpkgFindings
Affected versions and remediation
This report applies to supersignaturenature@1.0.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing supersignaturenature@1.0.6. 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.