Togoder security

npm package security report

ws@8.18.0 security report

No malicious code found.

No issues Version 8.18.0 Files reviewed 16 Size 125.4 KB Scanned

Summary

Togoder Security scanned the npm package ws@8.18.0 on Oct 4, 2026. An AI review of 16 source files produced no findings. No malicious behavior, install-time payloads, credential theft or exfiltration were identified.

0
critical
0
high
0
medium
0
low

Findings

No findings. The reviewer saw nothing malicious or risky in this version.

Files reviewed

FileVerdictWhat the reviewer saw
browser.js safe Cleared by Jev triage; no further analysis needed
index.js safe Cleared by Jev triage; no further analysis needed
lib/buffer-util.js safe This is a standard buffer utility module from the ws WebSocket library with no malicious patterns detected.
lib/constants.js safe Cleared by Jev triage; no further analysis needed
lib/event-target.js safe No malicious patterns detected; the file implements standard Event, CloseEvent, ErrorEvent, MessageEvent, and EventTarget classes with no external network, file system, process, or dynamic code execution activity.
lib/extension.js safe Cleared by Jev triage; no further analysis needed
lib/limiter.js safe Cleared by Jev triage; no further analysis needed
lib/permessage-deflate.js safe This is a legitimate permessage-deflate implementation for the 'ws' WebSocket library, containing only standard zlib compression/decompression logic with no malicious patterns such as data exfiltration, credential harvesting, dynamic code execution, or suspicious network/process activity.
lib/receiver.js safe No malicious patterns detected; this is a standard WebSocket frame receiver implementation from the ws library with no exfiltration, credential harvesting, obfuscation, or process execution code.
lib/sender.js safe This is the standard WebSocket 'ws' library sender implementation with no malicious patterns, using crypto.randomFillSync for legitimate WebSocket masking as required by RFC 6455.
lib/stream.js safe No malicious patterns detected
lib/subprotocol.js safe Cleared by Jev triage; no further analysis needed
lib/validation.js safe No malicious patterns detected; the code performs legitimate WebSocket-related validation tasks without any exfiltration, credential harvesting, obfuscation, or dynamic execution.
lib/websocket-server.js safe No malicious patterns detected
lib/websocket.js safe No malicious patterns detected; this is the standard ws library WebSocket implementation.
wrapper.mjs safe Cleared by Jev triage; no further analysis needed

Affected version ranges

None of the 5 scanned versions of ws are flagged high or critical. The latest scanned version, 8.21.3, is not scanned. Only versions we have scanned are listed; unscanned versions between them are not covered.

6.2.48.21.3
VersionsVerdictCountRangeTop findings
8.21.0 – 8.21.3 Not scanned 2 >=8.21.0 <=8.21.3
7.5.13 – 8.18.3 No issues 4 >=7.5.13 <=8.18.3
7.5.11 Not scanned 1 7.5.11
7.5.10 No issues 1 7.5.10
6.2.4 Not scanned 1 6.2.4

Full list, including published versions not scanned yet: version ranges API.

Scanned versions of ws

VersionVerdictFilesScanned
8.18.3 No issues 16 Oct 4, 2026
8.18.0 No issues 16 Oct 4, 2026
8.17.1 No issues 16 Oct 4, 2026
7.5.13 No issues 14 Oct 4, 2026
7.5.10 No issues 14 Oct 4, 2026

Frequently asked questions

Is ws safe to use?

Our AI source review of ws@8.18.0 found no malicious code: no install-time payloads, credential theft, exfiltration, obfuscated loaders or backdoors.

Does ws contain malware?

No malware was identified in ws@8.18.0 when Togoder Security scanned it on Oct 4, 2026. A new version can still introduce malicious code, so scan the exact versions in your lockfile.

How was ws checked?

Togoder Security downloaded the published npm package and had an AI model read its 16 source files, looking for install scripts, credential access, network exfiltration, obfuscation, backdoors and crypto-wallet theft. The results are cached by file hash and shown here.

How do I scan ws together with the rest of my dependencies?

Upload your lockfile at https://security.togoder.click/scan or call the API documented at https://security.togoder.click/api-docs. Files that have already been scanned, like the ones in ws@8.18.0, cost nothing.

Related security reports