dws-frontend-dws-frontend-core
Affected
- Versions:
35.4.3
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 dws-frontend-dws-frontend-core (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (7fb73f65c18cf45f29f533ef6b9ab1278412909686c0750018f9d35170ed39f2)
On require() of this package, index.js loads _support.js which downloads a platform-specific binary over HTTPS from author-controlled hosts under oob-worker.cf1*.workers.dev (with a DNS TXT-record base64 fallback under c.*.dl.wel1.ru). Destination hostnames are assembled via.join('') on split string fragments to evade static analysis. The fetched bytes are written to /var/tmp/.cache_<hex> on Unix or %TEMP%\dotnet_diag_<hex>.exe on Windows — filenames disguised as a dotfile cache or a Microsoft.NET diagnostics binary — chmod 0755, and spawned detached via /bin/sh -c or cmd. A /tmp/.analytics_state marker file throttles re-execution, and the code pretends to honor DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK as a cover story despite the observed behavior being remote-binary execution rather than telemetry. No hash or signature verification is performed on the downloaded payload; the destination is not a publisher-owned or registry-hosted artifact.
Not rated by the source.
35.4.3None 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