Summary
Togoder Security scanned the npm package @walletconnect/relay-auth@1.1.0 on Oct 4, 2026. An AI review of 3 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.
Findings
No findings. The reviewer saw nothing malicious or risky in this version.
Files reviewed
| File | Verdict | What the reviewer saw |
|---|---|---|
| dist/index.cjs.js | safe | The code is a legitimate cryptographic library implementation for JWT signing and verification using Ed25519, with no malicious patterns detected. |
| dist/index.es.js | safe | No malicious patterns detected; the code implements cryptographic primitives (hashing, Ed25519, JWT, multibase encoding) without any exfiltration, obfuscation, backdoors, or suspicious behavior. |
| dist/index.umd.js | safe | No malicious patterns detected |
Frequently asked questions
Is @walletconnect/relay-auth safe to use?
Our AI source review of @walletconnect/relay-auth@1.1.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.
Does @walletconnect/relay-auth contain malware?
No malware was identified in @walletconnect/relay-auth@1.1.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.
How was @walletconnect/relay-auth checked?
Togoder Security downloaded the published npm package and had an AI model read its 3 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.
How do I scan @walletconnect/relay-auth together with the rest of my dependencies?
Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in @walletconnect/relay-auth@1.1.0, cost nothing.