Which versions of cobrowsing-k8s-module are malicious?

The following npm versions of cobrowsing-k8s-module are flagged malicious: 35.6.2. Treat any of these as compromised.

How do I remediate cobrowsing-k8s-module if I installed it?

Remove cobrowsing-k8s-module from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed cobrowsing-k8s-module — how do I know if it already compromised me?

If cobrowsing-k8s-module 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 cobrowsing-k8s-module part of a known attack campaign?

Yes — cobrowsing-k8s-module is associated with the IN-MAL-2026-015118 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 cobrowsing-k8s-module 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 cobrowsing-k8s-module (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cobrowsing-k8s-module across your stack and pipelines.

Malicious package

cobrowsing-k8s-modulenpm

cobrowsing-k8s-module is a confirmed malicious npm package (MAL-2026-12655) that executes malicious code on install (malicious version 35.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cobrowsing-k8s-module (npm)

MAL-2026-12655

Immediate action

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

npm uninstall cobrowsing-k8s-module

What this malware does

On require of the package's main entry, bridge.js selects a platform-specific endpoint, reconstructs remote hostnames at runtime via array.join("") string-split obfuscation (oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf103-070.workers.dev, and sdk/ext/pkg/net.dl.wel1.ru), fetches an opaque binary over HTTPS, writes it to a hidden temp path with cover-story filenames (dotnet_diag.exe,.cache_,.analytics_state), chmods 0755, and spawns it detached via child_process spawn("/bin/sh") or spawn("cmd"). If HTTP fetch fails, the code falls back to a DNS-TXT covert channel that reads a chunk count from c.<domain> and reassembles base64-encoded binary chunks across numbered TXT records under *.dl.wel1.ru to bypass HTTP egress filters. No hash or signature verification is performed. The behavior is disguised as analytics/telemetry.

Malicious versions

1 flagged

35.6.2

Indicators of compromise (SHA-256)

6cde47afeee95884dc83b3dab22855db86950fd58756900af5100d1286a7c7be

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cobrowsing-k8s-module (version 35.6.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cobrowsing-k8s-module across your stack and pipelines.
If you installed it — respond
Remove cobrowsing-k8s-module from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If cobrowsing-k8s-module 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 cobrowsing-k8s-module 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. cobrowsing-k8s-module on npm has been identified as a malicious package (version 35.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015118

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cobrowsing-k8s-module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database