PkgRadar

npm · registry.npmjs.org

@requestnetwork/web3-signature

Js Decode Then Exec: base64 / atob / fromCharCode decode paired with eval / new Function in the same file — canonical obfuscated-loader pattern.

Why PkgRadar flagged 0.13.1-next.053cae94.0

SeveritySignalEvidence
highJs Decode Then Execbase64 / atob / fromCharCode decode paired with eval / new Function in the same file — canonical obfuscated-loader pattern. · package/dist/web3-signature.min.js

Scanned versions

VersionVerdictScoreScanned (UTC)
0.14.1-next.af792b64.0Low risk02026-06-09
0.14.1-next.f220532d.0Low risk02026-06-08
0.14.1-next.ba2344ff.0Low risk02026-06-05
0.14.1-next.ada584b1.0Low risk02026-06-05
0.14.0Low risk02026-06-03
0.13.1-next.053cae94.0Review132026-05-28
0.13.0Low risk02026-05-25
0.12.0Low risk02026-05-24
0.12.1-next.2d9d2486.0Low risk02026-05-24

Block this in CI

PkgRadar gates @requestnetwork/web3-signature (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @requestnetwork/[email protected]