Which versions of bigops-watchdog-angular are malicious?

The following npm versions of bigops-watchdog-angular are flagged malicious: 35.4.8. Treat any of these as compromised.

How do I remediate bigops-watchdog-angular if I installed it?

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

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

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

Malicious package

bigops-watchdog-angularnpm

bigops-watchdog-angular is a confirmed malicious npm package (MAL-2026-12855) that executes malicious code on install (malicious version 35.4.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-watchdog-angular (npm)

MAL-2026-12855

Immediate action

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

npm uninstall bigops-watchdog-angular

What this malware does

On require() of the package, index.js loads vendor.js which selects a platform-specific URL, downloads an opaque binary from one of several Cloudflare Workers hosts (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback channel over sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache<hex> or %TEMP%\dotnet_diag_<hex>.exe, chmod 0755, and spawned detached via /bin/sh -c or cmd. Endpoint hostnames are split into fragments and reassembled at runtime via Array.join('') to evade static scanners. No hash or signature verification is performed, the destinations are hardcoded and unrelated to any stated Angular/watchdog purpose, and the staged binaries use disguised cache/diagnostic filenames. The result is arbitrary attacker-controlled code execution on any machine that installs or imports the package.

Malicious versions

1 flagged

35.4.8

Indicators of compromise (SHA-256)

d7bfa2b0d9464df6662fddb4e969b42ef35465f2c70ba39943ac3fb0265aa781

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

Campaign

IN-MAL-2026-015528

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-watchdog-angular-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