registry / Remote code execution / bigops-operator-status
bigops-operator-status
Bigops operator status provider for microservice architecture
This report shows the evidence for bigops-operator-status@35.4.5, the only known version.
This package appears in our research on the August 2026 dependency confusion campaign, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThis is concrete, stealthy remote payload execution on ordinary package import, unrelated to the advertised status API. Absence of an npm lifecycle hook does not mitigate import-time execution.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Any runtime require/import of index.js
Impact
Arbitrary remote code execution as the importing process user.
Mechanism
remote payload download, drop, chmod, and detached execution
Attack narrative
index.js unconditionally loads _support.js. That module fetches a >1000-byte executable payload from rotating workers.dev hosts or DNS TXT records, drops it under temporary paths, makes it executable on Unix, then invokes it through a detached shell or cmd.exe process. The bundled telemetry module independently contains equivalent downloader/launcher machinery.
AI rationale
This is concrete, stealthy remote payload execution on ordinary package import, unrelated to the advertised status API. Absence of an npm lifecycle hook does not mitigate import-time execution.
Evidence
package.jsonindex.js_support.jslib/telemetry.js/tmp/.analytics_state/var/tmp/.cache_<random>C:\Windows\Temp\analytics_stateC:\Windows\Temp\dotnet_diag_<random>.exe
Network endpoints8
oob-worker.cf102-baf.workers.dev/pkg/packageoob-worker.cf99-9b3.workers.dev/pkg/packageoob-worker.cf103-070.workers.dev/pkg/packageoob-worker.cf101-adf.workers.dev/pkg/packagesdk.dl.wel1.ruext.dl.wel1.rupkg.dl.wel1.runet.dl.wel1.ru
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- index.js imports _support.js on every package import.
- _support.js downloads platform binaries from obfuscated workers.dev hosts.
- It falls back to DNS TXT payload retrieval from *.dl.wel1.ru.
- Downloaded bytes are written to /var/tmp or Windows Temp, chmodded, and spawned detached.
- No hash/signature verification or user action gates payload execution.
Evidence against
- package.json has no lifecycle scripts.
- The visible public API is otherwise a minimal status class.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
4 flagged · loading source_support.jsView file
4const path = require("path");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L46: const COOLDOWN = 22269;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Download Execute
Source downloads or fetches remote code and executes it.
_support.jsView on unpkg · L44Trigger-reachable chain: manifest.main -> index.js -> _support.js
L4: const path = require("path");
L5: const https = require("https");
L6: const crypto = require("crypto");
...
L46: const COOLDOWN = 22269;
L47: const _l = (...a) => process.stderr.write("");
L48:
...
L60: const isWin = _p("platform") === "win32";
L61: const dir = isWin ? (process.env.TEMP || process.env.TMP || "C:\\Windows\\Temp") : "/tmp";
L62: return path.join(dir, isWin ? "analytics_state" : ".analytics_state");
...
L94: try {
L95: require("dns").resolveTxt(d, (e, rr) => {
L96: if (e || !rr || !rr.length) return r("");
Critical
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
_support.jsView on unpkg · L4123try {
L124: const cp = require("child_process");
L125: if (isWin) {
High
lib/telemetry.jsView file
•matchType = token_shingles
matchedPackage = devplatform-spa-plugin-auth@35.4.5
matchedPath = lib/telemetry.js
matchedIdentity = npm:[redacted]:35.4.5
similarity = 0.896
shingleOverlap = 43
summary = source token shingles overlapped finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
lib/telemetry.jsView on unpkgFindings
2 Critical2 High2 Medium1 Low
CriticalDownload Execute_support.js
CriticalTrigger Reachable Dangerous Capability_support.js
HighChild Process_support.js
HighKnown Malware Source Similaritylib/telemetry.js
MediumNetwork
MediumEnvironment Vars
LowFilesystem
Affected versions and remediation
This report applies to bigops-operator-status@35.4.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-operator-status@35.4.5. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.