secp256k1-lib
logger tool for validation entry
This report shows the evidence for secp256k1-lib@1.0.3. 4 of 4 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 2mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-14255 confirms this npm version as malicious.
Independent LPM AI assessment
SuspiciousIndependent AI assessment: suspicious. LPM AI assessed this version as suspicious; the assessments disagree.
The concealed outbound request and unrelated package documentation create unresolved security risk, but the source does not establish automatic theft or another concrete malicious chain.
Independent scan evidence
public snapshot- index.js is deliberately obfuscated.
- index.js imports axios and builds a hidden API_BASE_URL.
- Exported connect() performs an axios GET to that URL plus caller input.
- README.md references a different package: evm_account.
- package.json has no lifecycle hooks.
- Network call is only in exported connect(), not import-time.
- No source evidence of env/file harvesting, shell execution, or persistence.
Source & flagged code
2 flagged · loading sourceSource contains an obfuscator-style string-array loader that reconstructs and executes hidden code.
index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to secp256k1-lib@1.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing secp256k1-lib@1.0.3. 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.