Which versions of @velkov/isows are malicious?

The following npm versions of @velkov/isows are flagged malicious: 1.0.10. Treat any of these as compromised.

How do I remediate @velkov/isows if I installed it?

@velkov/isows is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @velkov/isows — how do I know if it already compromised me?

If @velkov/isows was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @velkov/isows part of a known attack campaign?

Yes — @velkov/isows is associated with the IN-MAL-2026-010370 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @velkov/isows across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @velkov/isows (version 1.0.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @velkov/isows across your stack and pipelines.

Malicious package

@velkov/isowsnpm

Malicious code in @velkov/isows (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10524

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @velkov/isows

What this malware does

Package is published as @velkov/isows while its README, repository (wevm/isows), description ("Isomorphic WebSocket"), and author (jxom.eth) impersonate the legitimate isows package. The legitimate upstream utils.ts is an 8-line getNativeWebSocket helper; in this package, _cjs/utils.js and _esm/utils.js append ~50KB of obfuscator.io-style payload (rotated string array a4(), base64+RC4 decoder a5(), debugger-trap class, while(!![]) loops). The payload runs at top level whenever the package is required or imported (the package.json main is ./_cjs/index.js, which loads ./utils.js). Behavior: re-execs Node with a sentinel env var, dynamically loads https/fs/os/child_process/path/crypto, issues an HTTPS GET to an RC4-decoded host/path, streams the response to a hostname-derived filename under os.tmpdir(), validates a sha256 from a sidecar JSON fetched from the same attacker-controlled host (attacker controls both payload and verification), AES-256-GCM-decrypts the bytes with a key XOR-derived from four embedded 32-byte buffers, chmods 0o755, and spawns the binary {detached:true, stdio:'ignore', windowsHide:true} so it survives the parent process. Error-handling stubs are empty to suppress diagnostics. This is the canonical typosquat-plus-dropper supply-chain attack pattern: any installer or transitive consumer that loads @velkov/isows runs attacker-controlled native code on their machine.

Malicious versions

1 flagged

1.0.10

Indicators of compromise (SHA-256)

4fee1d7d5125231d00f9c5f9afe9817b76900ca385b7d077bb4b8bcf3d9ca660

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @velkov/isows (version 1.0.10). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @velkov/isows across your stack and pipelines.
If you installed it — respond
@velkov/isows is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @velkov/isows was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @velkov/isows before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @velkov/isows on npm has been identified as a malicious package (version 1.0.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010370

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @velkov/isows-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring