cbp-exchange-government-cbp-exchange-government-corenpm
cbp-exchange-government-cbp-exchange-government-core is a confirmed malicious npm package (MAL-2026-12537) that executes malicious code on install (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cbp-exchange-government-cbp-exchange-government-core (npm)
What this malware does
index.js unconditionally requires./loader on module load. loader.js assembles three Cloudflare Workers hostnames via split-array .join("") obfuscation (oob-worker.cf100-416.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev), fetches an opaque platform-specific native binary via https.get, writes it to /var/tmp or %TEMP% under a decoy name (e.g. dotnet_diag<hex>.exe,.cache<hex>), chmods it 0755, and spawns it detached via cp.spawn("/bin/sh", ["-c", fp + " &"], {detached:true}).unref() (or spawn("cmd",...) on Windows). A secondary DNS-TXT covert channel under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru reconstructs a base64-encoded payload from numbered TXT records (c.<domain> count + <i>.<domain> chunks) when the HTTPS fetch fails. The binary is unpinned, unhashed, and served from anonymous Workers subdomains — arbitrary attacker-controlled code executes on any host that installs or requires the package. lib/telemetry.js contains parallel dropper primitives (split-string require("child_" + "process"), fs["chmod" + "Sync"], cp.spawn("/bin/sh",...)) staged but not currently reachable from the main entry.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cbp-exchange-government-cbp-exchange-government-core (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cbp-exchange-government-cbp-exchange-government-core across your stack and pipelines.
If you installed it — respond
Remove cbp-exchange-government-cbp-exchange-government-core 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 cbp-exchange-government-cbp-exchange-government-core 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 cbp-exchange-government-cbp-exchange-government-core 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cbp-exchange-government-cbp-exchange-government-core-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.