registry / @leofcoin/chain / 1.10.16
@leofcoin/chain@1.10.16
Official javascript implementation
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no install lifecycle hooks or concrete attack behavior. The flagged dynamic execution is in the contract worker, while the browser network calls are in local-daemon and peer-discovery helpers; the public-address lookup is guarded by a condition that does not pass for the initialized address object.
Static reason
One or more suspicious static signals were detected.
Trigger
Contract deployment or runtime use of browser peer-discovery helpers.
Impact
These inspected paths support chain and peer-discovery features; no concrete harmful effect was established.
Mechanism
A worker instruments and evaluates contract source; browser helpers check for a local daemon and contain peer-location lookup logic.
AI rationale
Source inspection found no install lifecycle hooks or concrete attack behavior. The flagged dynamic execution is in the contract worker, while the browser network calls are in local-daemon and peer-discovery helpers; the public-address lookup is guarded by a condition that does not pass for the initialized address object.
Evidence
exports/workers/machine-worker.jsexports/browser/workers/machine-worker.jsexports/browser/node-browser-DWSdi-XP.jsexports/browser/chain.js
Network endpoints3
127.0.0.1:1000/api/versionicanhazip.com/whereis.leofcoin.org/
Decision evidence
public snapshotAI called this Clean at 82.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes chain and worker entrypoints and has no npm lifecycle hook in its scripts.
- The flagged worker dynamically evaluates instrumented contract source as part of contract deployment, matching the package’s chain functionality.
- The browser bundle’s local-daemon and peer-geolocation requests are in runtime helpers; the public-address lookup is conditional on a value that is already an object.
- The inspected dependencies provide WebRTC and cryptographic primitives used by the package; no concrete attack behavior was identified.
Evidence against
- The worker uses dynamic code generation, and browser helpers contain network requests, but the inspected contexts show contract execution and peer discovery behavior.
Behavioral surface
CryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkWebSocket
HighEntropyStringsTelemetry
Source & flagged code
5 flaggedexports/browser/workers/machine-worker.jsView file
8534const source = instrumentContractSource(new TextDecoder().decode(decoded.contract));
L8535: const func = new Function('__lfcMeter', 'Date', 'crypto', source);
L8536: const Contract = func(meterBridge, dateBridge, cryptoBridge);
Low
Eval
Package source references a known benign dynamic code generation pattern.
exports/browser/workers/machine-worker.jsView on unpkg · L8534exports/browser/node-browser-DWSdi-XP.jsView file
453* ```js
L454: * const {createHash} = await import('@leofcoin/crypto')
L455: * createHash(data, algorithm)
Medium
Dynamic Require
Package source references dynamic require/import behavior.
exports/browser/node-browser-DWSdi-XP.jsView on unpkg · L453exports/browser/chain.jsView file
Findings
1 High3 Medium8 Low
HighCross File Remote Execution Contextexports/browser/chain.js
MediumDynamic Requireexports/browser/node-browser-DWSdi-XP.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvalexports/browser/workers/machine-worker.js
LowFilesystem
LowHigh Entropy Strings
LowTelemetry
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidenceexports/workers/machine-worker.js
Affected versions and remediation
This report applies to @leofcoin/chain@1.10.16.
See all versions of @leofcoin/chain for other recorded verdicts.
- Review the evidence and your use of @leofcoin/chain@1.10.16 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.