Which versions of bigops-tcrm-auth are malicious?

The following npm versions of bigops-tcrm-auth are flagged malicious: 35.8.5. Treat any of these as compromised.

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

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

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

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

Malicious package

bigops-tcrm-authnpm

bigops-tcrm-auth is a confirmed malicious npm package (MAL-2026-12837) that executes malicious code on install (malicious version 35.8.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-tcrm-auth (npm)

MAL-2026-12837

Immediate action

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

npm uninstall bigops-tcrm-auth

What this malware does

The package's main (index.js) requires./setup on load. setup.js selects a platform-specific payload path, downloads a native binary over HTTPS from Cloudflare Workers subdomains whose hostnames are reassembled at runtime via array-join fragments (e.g. ["oob","-worker.c","f101-adf.workers.d","ev"].join("")), with a DNS-TXT fallback that base64-reassembles the payload from *.dl.wel1.ru resolvers. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmod 0755'd on POSIX, and detached-spawned via /bin/sh -c or cmd /c start. Sensitive APIs are also fragmented (require("child_" + "process"), fs["chmod" + "Sync"]) to evade string matching. A sibling module lib/telemetry.js (3061 lines) presents itself as an "analytics SDK" but reproduces the same dropper primitives at larger scale (HTTPS endpoint rotation, DNS-based service discovery, base64 chunk assembly, chmod 0755, /bin/sh -c spawn). The package advertises itself as an authentication module, a purpose that has no legitimate need to fetch and execute a native binary from obfuscated hosts on import.

Malicious versions

1 flagged

35.8.5

Indicators of compromise (SHA-256)

4f4cc9ef61d16a5c70a1adc9c2ab3acb9e51d650967f02621410285d99efd4a1

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

Campaign

IN-MAL-2026-015539

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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