Which versions of bigops-chat-transfer are malicious?

The following npm versions of bigops-chat-transfer are flagged malicious: 35.3.6. Treat any of these as compromised.

How do I remediate bigops-chat-transfer if I installed it?

Remove bigops-chat-transfer 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 bigops-chat-transfer — how do I know if it already compromised me?

If bigops-chat-transfer 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 bigops-chat-transfer part of a known attack campaign?

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

Malicious package

bigops-chat-transfernpm

bigops-chat-transfer is a confirmed malicious npm package (MAL-2026-12156) that executes malicious code on install (malicious version 35.3.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-chat-transfer (npm)

MAL-2026-12156

Immediate action

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

npm uninstall bigops-chat-transfer

What this malware does

On require() of bigops-chat-transfer, platform.js reconstructs one of three Cloudflare workers.dev hostnames from split string fragments (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev), downloads a platform-specific native binary over HTTPS, and — if HTTPS fails — falls back to a DNS-TXT covert channel under *.dl.wel1.ru that reconstructs a base64-encoded binary from sequentially numbered TXT records. The downloaded bytes are written to /var/tmp/.cache<uid> on Unix or %TEMP%/dotnet_diag_<uid>.exe on Windows, chmod 0755'd, and spawned detached via /bin/sh -c or cmd /c start. A.analytics_state lock file provides rate-limit persistence, and the naming (dotnet_diag, analytics_state) is a cover story masquerading as.NET diagnostics telemetry. Destination hosts are not the package publisher's infrastructure, the fetched executable is opaque and unverified, and execution is triggered by ordinary import of the module.

Malicious versions

1 flagged

35.3.6

Indicators of compromise (SHA-256)

1d8d11b7e8abee5caddc5c2f1765fa7f10d40c8cce0ef1cafed55fe31537be94

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 bigops-chat-transfer (version 35.3.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bigops-chat-transfer across your stack and pipelines.
If you installed it — respond
Remove bigops-chat-transfer 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 bigops-chat-transfer 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 bigops-chat-transfer 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. bigops-chat-transfer on npm has been identified as a malicious package (version 35.3.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014411

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-chat-transfer-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