boxy-mif-tokens
Affected
- Versions:
35.7.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 boxy-mif-tokens (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (e4e9fe90e4c6a7334c75fffb7bd07fdeb785a35b9fc2c1a9e5ce74265296d1c7)
On require() of this package, index.js loads _bridge.js which downloads a platform-specific native executable from string-split obfuscated Cloudflare Workers hostnames (reassembled at runtime via ["...","..."].join("")) with a DNS TXT-record base64 fallback channel over *.dl.wel1.ru. The fetched bytes are written to /tmp or %TEMP% under decoy names such as.cache_<hex> and dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c '<path> &' on Unix or cmd /c start /b on Windows, using child_process.spawn(...).unref(). The package presents itself as a token SDK and has no legitimate need to fetch and execute an unpinned, unhashed native binary from non-publisher infrastructure. Hostname reassembly, DNS-over-TXT delivery fallback, hidden staging paths, and decoy filenames are evasion characteristics of a dropper, not of a normal SDK download.
Not rated by the source.
35.7.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