@sarex-team/viewer
Affected
- Versions:
9.9.11
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 @sarex-team/viewer (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (04b67de30d08d48f32be517383d6940c8179d2269ea7a1720346eacc2e8c28d5)
The package runs a DNS-based beacon that leaks the installer's OS username, hostname, and current-working-directory basename to the hardcoded attacker-controlled domain oob.sl4x0.xyz. lib/core.js collects os.userInfo().username, os.hostname(), and process.cwd(), joins them as subdomain labels under oob.sl4x0.xyz, and issues a dns.resolve4() lookup so the encoded values are exfiltrated via DNS. The destination domain and the module/API names ('os', 'dns', 'process', 'userInfo', 'hostname', 'cwd', 'resolve4') are reconstructed from numeric char-code arrays in lib/b02e30.js and lib/6ad264.js solely to conceal them. Execution is zero-interaction: package.json declares scripts.install: 'node index.js', and index.js top-level requires./lib/core inside a try/catch that swallows errors, so the beacon fires on npm install and again on every require() of the package while the install appears clean.
Not rated by the source.
9.9.11None 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