node_cryptography
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in node_cryptography (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (1e10a704c94a9f7a4f6344a67e3867cd87b21be574e81bbdccdc6b5ca48f65a2)
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.
Not rated by the source.
1.0.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0