npm-hex-utils
Affected
- Versions:
1.1.1
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 npm-hex-utils (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (6a0f1f9004b6a502c144d4d475e89a3956905aebf51fb2696d4ba05c21613727)
The package's postinstall runs runtime.js, which POSTs os.hostname(), os.userInfo().username, os.platform()+os.arch(), Node version, and OS release to https://steel-mere-4155.ricardorichp.workers.dev/report, then fetches an encrypted blob from https://steel-mere-4155.ricardorichp.workers.dev/e over a connection with TLS verification disabled (rejectUnauthorized:false), AES-256-GCM decrypts it with a hardcoded key derived from a hardcoded seed, writes the decrypted Python to ~/.cache/hex-encode-utils/modules/runtime.py, and spawns python detached with stdio ignored to execute it. Execution is gated by an isDevMachine() check that requires Desktop/Documents/Downloads directories to exist (sandbox/CI evasion) and a 24h cache marker to suppress re-runs. Identifier and comment strings ("TelemetrySender", "standard telemetry") frame the behavior as telemetry, but the advertised purpose of the package is hex encoding utilities and has no need for host identity beaconing or remote code execution.
Not rated by the source.
1.1.1None 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