VDB
GCVE-110-OSM-2026-10757
GCVE-110-OSM-2026-10757
Advisory PublishedCVSS 5.4/10
The package presents itself as a Node.js cryptography helper and depends on ethers, encouraging callers to pass cryptographic or wallet material to its sole exported async function. That function forwards the caller's argument via axios to an API_BASE_URL assembled at runtime from ~13 fragments produced by an obfuscator.io RC4 string-array decoder. The entire ~30 KB index.js is wrapped in the standard obfuscator.io scheme (RC4+base64 string array, hex-escaped literals, wrapped index accessors, array-rotation IIFE, and a self-defending RegExp function-body anti-tamper check) whose only purpose here is to hide the destination URL. The caller does not configure this destination and is not informed of it; normal use of the advertised API silently leaks the caller's cryptographic inputs to an author-controlled host.
Judge assessment: This package is highly suspicious because the sole entrypoint `index.js` is wrapped in `obfuscator.io`-style RC4/base64 string-array decoding, heavy `_0x` hex variables, and anti-tamper self-defending code, which is atypical for a normal cryptography helper. The OSV advisory (`MAL-2026-14276`) claims the exported async function forwards caller-supplied crypto/wallet material via `axios` to a runtime-assembled `API_BASE_URL`, but the evidence provided here does not include recovered IOCs or the exfil destination, so I cannot confirm the theft path outright from the visible content alone. The attacker model is plausible credential/crypto-data exfiltration by the package author, especially given the brand-new npm account (`cryptozkeedz`) and one-off publication, but the static payload excerpt is truncated before the network sink is shown. I would treat this as a likely malicious loader with hidden exfiltration behavior, but keep the verdict at suspicious because the specific outbound endpoint is not visible in the supplied evidence.
ENTRY
index.js (main: index.js)
OBFUSCATION
- Obfuscation (osm-deobfuscator): obfuscator-io in index.js
- Hex Encoded Strings in index.js: "'\x57\x37\x37\x64\x56\x66\x6c\x64\x4d\x4b\x75\x36\x6e\x33\x46\x64\x4d\x57\x70\x6..."
- Unicode Escape Obfuscation in index.js: "\x57\x37\x37\x64\x56\x66\x6c\x64\x4d\x4b\x75\x36\x6e\x33\x46\x64\x4d\x57\x70\x64..."
- Obfuscation: obfuscator.io in index.js
- Decoded Hex Escape Content in index.js (x143)
- Strings Extracted from Deobfuscated Code in index.js
- Obfuscation patterns: hexVariables, hexHeavy in index.js
PAYLOAD FILES
index.js
Weaknesses (CWE)
CWE-506Embedded Malicious Code
Risk Scores
CVSS 3.1
5.4/10
Medium · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
Affected Products
| Vendor | Product | Versions | Platforms |
|---|---|---|---|
| unknown | node_cryptography | all (affected) | — |
Aliases
Browse GCVE Records
69,369 records in the GCVE database · Updated August 25, 2026
No matching records found.
Explore Further
Investigate this vulnerability in the interactive console or download the raw GCVE record.