claims-block-visibility
Affected
- Versions:
35.3.8
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 claims-block-visibility (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (b6afd966a220b14c0d01a2132af36d206eee200ab806d61443b66379e560b324)
On require('claims-block-visibility'), index.js loads _polyfill.js which unconditionally runs a setup routine that selects an OS-specific endpoint, downloads a binary from one of several string-concatenation-obfuscated hosts under *.workers.dev, and falls back to a chunked base64-over-DNS-TXT channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru when HTTPS is unavailable. The fetched bytes are written to a temp path disguised as.cache_<hex> or dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd.exe with unref(). Destination hostnames are assembled from split string arrays (e.g. ['oob','-worker','.cf103-',...].join('')) and require('child_process') is masked as require('child_'+'process'). A cache-stamp file is written under a benign '.analytics_state' name. The behavior fires on module load, giving any consumer that requires this package a fetch-and-execute of opaque attacker-controlled native code.
Not rated by the source.
35.3.8None 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