Which versions of cobrowsing-redis-module are malicious?

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

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

cobrowsing-redis-module establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

cobrowsing-redis-modulenpm

cobrowsing-redis-module is a confirmed malicious npm package (MAL-2026-12657) that opens a backdoor for remote access (malicious version 35.4.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cobrowsing-redis-module (npm)

MAL-2026-12657

Immediate action

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

npm uninstall cobrowsing-redis-module

What this malware does

index.js unconditionally requires./loader on import. loader.js selects a platform-specific endpoint, assembles C2 hostnames at runtime from split string arrays (e.g. ["oob-worker.cf99-9b3.workers",".d","ev"].join("")) pointing at oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, and oob-worker.cf100-416.workers.dev, downloads bytes via https.get, writes them to /var/tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe on Windows,.cache<hex> on POSIX), chmods 0755, and spawns the file detached via /bin/sh -c or cmd.exe. When HTTPS fails, a DNS-TXT covert channel over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru reassembles the payload from base64 TXT chunks (c.<domain> for chunk count, <i>.<domain> for each chunk) via Buffer.from(...,'base64'). No hash or signature verification is performed. A.analytics_state stamp file and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env-var gates are used as cover-story framing; the destinations and behavior are unrelated to any Redis or cobrowsing functionality. The package name and README present it as an internal Redis wrapper while the sibling _loader.js contains only the dropper.

Malicious versions

1 flagged

35.4.7

Indicators of compromise (SHA-256)

502c907b28a2866d4fc67be93a6417e535336938ce3e8c23f0f95e927c6711b6

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cobrowsing-redis-module (version 35.4.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cobrowsing-redis-module across your stack and pipelines.
If you installed it — respond
cobrowsing-redis-module establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If cobrowsing-redis-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-redis-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-redis-module on npm has been identified as a malicious package (version 35.4.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015107

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cobrowsing-redis-module-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database