bigops-create-manifest
This report shows the evidence for bigops-create-manifest@35.2.4, 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.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12037 confirms this npm version as malicious.
Advisory
MAL-2026-12037
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in bigops-create-manifest (npm)
Details
On require, index.js loads _polyfill.js which selects a platform-specific endpoint, downloads an opaque native binary over HTTPS 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 covert-channel fallback that reads base64-encoded chunks from sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru. The fetched bytes are written to a randomized filename disguised as dotnet_diag_<hex>.exe on Windows or.cache_<hex> under /var/tmp on Unix, chmod 0755, and spawned detached via /bin/sh -c or cmd. C2 hostnames and resolver domains are assembled at runtime via split-string array joins; artifact naming, an analytics_state marker, and DISABLE_TELEMETRY env checks frame the operation as diagnostics. The package's advertised purpose (a manifest wrapper) has no need for downloading and executing a native binary from third-party infrastructure.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to bigops-create-manifest@35.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing bigops-create-manifest@35.2.4. 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: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.