Which versions of specials-obid-webpack are malicious?

The following npm versions of specials-obid-webpack are flagged malicious: 20.5.4. Treat any of these as compromised.

How do I remediate specials-obid-webpack if I installed it?

specials-obid-webpack is a typosquat — you almost certainly intended a legitimately-named package. Remove specials-obid-webpack, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed specials-obid-webpack — how do I know if it already compromised me?

If specials-obid-webpack 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 specials-obid-webpack part of a known attack campaign?

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

Malicious package

specials-obid-webpacknpm

specials-obid-webpack is a confirmed malicious npm package (MAL-2026-12072) that typosquats a legitimate package to trick installs (malicious version 20.5.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in specials-obid-webpack (npm)

MAL-2026-12072

Immediate action

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

npm uninstall specials-obid-webpack

What this malware does

On require of the package, _vendor.js selects a URL path by host platform, downloads a binary over HTTPS from destination hostnames assembled at runtime via array .join("") string-splits (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf103-070.workers.dev), writes it to a disguised temp path (/tmp/.cache_<rnd> on Unix, %TEMP%\dotnet_diag_<rnd>.exe on Windows), fs.chmodSync(savePath, 0o755), and spawns it detached via spawn("/bin/sh",...) or spawn("cmd",...). A DNS-TXT covert-channel fallback reassembles base64 chunks from *.dl.well1.site. A parallel dropper implementation is bundled at lib/telemetry.js using the same DNS-base64 reassembly, cp.spawn("/bin/sh", ["-c", filePath + " &"]), and split identifiers ("child_"+"process", "chmod"+"Sync") under a telemetry cover story. Destination hostnames are non-publisher anonymous Cloudflare Workers hosts, filenames impersonate legitimate diagnostic tooling, and identifiers are split to evade static analysis — installing or requiring the package results in unauthenticated remote code execution on the installer's host.

Malicious versions

1 flagged

20.5.4

Indicators of compromise (SHA-256)

ef5ac97b682821ce99ff6152a28467cd5ec91903d061ba1fc70ef7a3e6b9be03

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for specials-obid-webpack (version 20.5.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging specials-obid-webpack across your stack and pipelines.
If you installed it — respond
specials-obid-webpack is a typosquat — you almost certainly intended a legitimately-named package. Remove specials-obid-webpack, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If specials-obid-webpack 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 specials-obid-webpack 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. specials-obid-webpack on npm has been identified as a malicious package (version 20.5.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011517

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks specials-obid-webpack-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