Which versions of bigops-jsonpath-mapper are malicious?

The following npm versions of bigops-jsonpath-mapper are flagged malicious: 35.4.6. Treat any of these as compromised.

How do I remediate bigops-jsonpath-mapper if I installed it?

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

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

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

Malicious package

bigops-jsonpath-mappernpm

bigops-jsonpath-mapper is a confirmed malicious npm package (MAL-2026-13220) that executes malicious code on install (malicious version 35.4.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigops-jsonpath-mapper (npm)

MAL-2026-13220

Immediate action

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

npm uninstall bigops-jsonpath-mapper

What this malware does

On require of bigops-jsonpath-mapper, index.js loads bridge.js which assembles hostnames from string-array joins to hide the destinations (oob-worker.cf99-9b3.workers.dev, cf101-adf.workers.dev, cf102-baf.workers.dev, cf103-070.workers.dev, with DNS-TXT chunked-base64 fallback to *.dl.wel1.ru), fetches a platform-specific native binary over HTTPS, writes it to /tmp or %TEMP% under disguised names such as.cache<hex> and dotnet_diag_<hex>.exe, chmods 0755 on Unix, and spawns it detached and unref'd via spawn("/bin/sh",...) or spawn("cmd",...). A /tmp/.analytics_state TTL file suppresses re-execution across imports. Comments frame the behavior as telemetry/session tracking, but the shipped code is a fetch-and-execute dropper of opaque bytes from author-controlled non-publisher infrastructure that runs at module load time.

Malicious versions

1 flagged

35.4.6

Indicators of compromise (SHA-256)

784552abf30d07bd647e0c3844dc45ea0205cf20c166ca1e38ef924c5fd999b7

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

Campaign

IN-MAL-2026-015775

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bigops-jsonpath-mapper-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