Which versions of bigops-tcrm-permissions are malicious?

The following npm versions of bigops-tcrm-permissions are flagged malicious: 35.5.1, 35.6.1. Treat any of these as compromised.

How do I remediate bigops-tcrm-permissions if I installed it?

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

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

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

Malicious package

bigops-tcrm-permissionsnpm

bigops-tcrm-permissions is a confirmed malicious npm package (MAL-2026-12839) that opens a backdoor for remote access (malicious versions 35.5.1, 35.6.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-tcrm-permissions (npm)

MAL-2026-12839

Immediate action

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

npm uninstall bigops-tcrm-permissions

What this malware does

On require of bigops-tcrm-permissions, index.js loads runtime.js which fetches a platform-specific binary from hardcoded Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT base64 fallback via sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru, writes the bytes to /var/tmp or %TEMP% under a hidden/decoy name, chmods the file 0755, and spawns it detached via /bin/sh -c or cmd. No hash or signature verification is performed, and the destinations are not associated with the package publisher. Destination hostnames and dangerous API names (require("child"+"process"), fs["chmod"+"Sync"]) are reassembled at runtime from string fragments to evade static matching. lib/telemetry.js contains a duplicate dropper flow (base64-assembled chunks, write, chmod 755, spawn /bin/sh detached) under an 'Analytics SDK' cover story, providing a second execution path against the same C2 infrastructure. The advertised purpose is a permissions SDK; dropping and executing native binaries from unrelated infrastructure is inconsistent with that purpose.

Malicious versions

2 flagged

35.5.135.6.1

Indicators of compromise (SHA-256)

a20b19aa6d3666cf99d03011aefd683f0d560b45dac6f27c2915dd68dd95bc0d

8ed0adaa078f72d10e3e479f54d4f71f5cb9b7a1f78c0007305c505cb8dc074d

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

Campaign

IN-MAL-2026-015540IN-MAL-2026-015888

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-tcrm-permissions-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