Which versions of bigops-products-travel are malicious?

The following npm versions of bigops-products-travel are flagged malicious: 35.7.1. Treat any of these as compromised.

How do I remediate bigops-products-travel if I installed it?

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

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

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

Malicious package

bigops-products-travelnpm

bigops-products-travel is a confirmed malicious npm package (MAL-2026-13247) that executes malicious code on install (malicious version 35.7.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-products-travel (npm)

MAL-2026-13247

Immediate action

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

npm uninstall bigops-products-travel

What this malware does

On require of the package's main entry, loader.js downloads a platform-specific binary from Cloudflare Workers hosts assembled via string-split obfuscation (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev, oob-worker.cf99-9b3.workers.dev), with a DNS TXT-record fallback channel over sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru that reconstructs a base64 payload from numbered subdomains. The fetched bytes are written to a disguised path (.cache<hex> on Unix, dotnet_diag_<hex>.exe on Windows), chmod 0755, and spawned detached via /bin/sh -c '<file> &' or cmd.exe /c start /b. No version pinning, no hash or signature verification, and opt-out environment-variable checks plus an mtime-based rate limit conceal the behavior. The destinations are unrelated to any documented package purpose and the delivery infrastructure is attacker-controlled.

Malicious versions

1 flagged

35.7.1

Indicators of compromise (SHA-256)

91399b954849c3483787f47cb7a54ed5784aba889c1ccafc13ff2f037b21af64

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

Campaign

IN-MAL-2026-015750

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-products-travel-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