layer2-sdk
Multi-chain Layer 2 SDK — bridge helpers, gas estimation, chain detection for Arbitrum, Optimism, Base, zkSync, Polygon zkEVM
This report shows the evidence for layer2-sdk@1.0.1. 2 of 2 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection confirms an import-time persistence and credential-exfiltration chain concealed behind benign SDK functions. The lack of lifecycle hooks does not mitigate runtime execution on import.
Decision evidence
public snapshot- `index.js` runs an import-time delayed dropper.
- `index.js` decodes `test/fixtures/keypairs.dat` into a hidden executable.
- Decoded payload searches wallet, env, SSH, and key files.
- Payload encrypts findings and posts them to `api.pinata.cloud`.
- Payload uses Gist/IPFS activation checks and persists via cron, Scheduled Tasks, or launchd.
- `package.json` has no lifecycle scripts.
- The advertised chain/RPC helpers are benign but are followed by the hidden payload.
Source & flagged code
4 flagged · loading sourceSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
index.jsView on unpkg · L3Source file is highly similar to a previously finalized malicious package; route for source-aware review.
index.jsView on unpkgFindings
Affected versions and remediation
This report applies to layer2-sdk@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing layer2-sdk@1.0.1. 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.