sn-flow-client
Affected
- Versions:
1.0.1,1.0.2,10.10.10,20.5.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 sn-flow-client (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (d2c83ae0b3aa74be7de2508ec17549e3bc00e40edd30c62322e91be77ea48e69)
package.json declares a preinstall hook ("preinstall": "node index.js") that runs index.js automatically on npm install. index.js requires child_process, os, http, and https, then collects installer host identity — os.hostname(), process.platform, os.arch(), os.homedir(), os.userInfo() (username/uid/gid/shell), and the output of whoami / id / cwd via child_process — and POSTs the collected JSON to https://ypraooa298eigl12zisuxg2f76dx1npc.oastify.com/detox56. oastify.com is the Burp Collaborator out-of-band interaction domain; the random subdomain is an attacker-controlled OAST listener. The package has empty author/description/license metadata, no legitimate functionality, and a plausibly-internal-sounding name (sn-flow-client) — consistent with a dependency-confusion probe rather than a real client library. Installing this package causes immediate outbound transmission of installer host/user identifiers to an attacker-controlled endpoint with no user consent.
Source: ossf-package-analysis (40af2ecf250ffc74b1566c2e1b013c1fb2f8e1917dc5878511d1dbaf791c0c48)
The OpenSSF Package Analysis project identified 'sn-flow-client' @ 10.10.10 (npm) as malicious.
It is considered malicious because:
Not rated by the source.
1.0.1, 1.0.2, 10.10.10, 20.5.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