sn-flow-client
This report shows the evidence for sn-flow-client@1.0.2. 4 of 4 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2024-9443 confirms this npm version as malicious.
Advisory
MAL-2024-9443
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in sn-flow-client (npm)
Details
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:
- The package communicates with a domain associated with malicious activity.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to sn-flow-client@1.0.2.
The same advisory and Firewall decision cover 4 recorded versions
10.10.10, 20.5.1, 1.0.2, 1.0.1
The versions list below shows the verdict for each recorded version.
- Avoid installing sn-flow-client@1.0.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.