travel-core-utils-objectnpm
travel-core-utils-object is a confirmed malicious npm package (MAL-2026-12487) that executes malicious code on install (malicious version 20.3.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in travel-core-utils-object (npm)
What this malware does
The package's main entry (index.js) has a side-effect require of _bridge.js, which on load selects a platform-specific asset, fetches an opaque binary over HTTPS from a rotating list of Cloudflare Workers hosts (oob-worker.cf*.workers.dev and *.dl.well1.site, assembled via array-join string-splitting to evade static matching, with a DNS-over-TXT fallback that base64-reassembles the payload URL from TXT records), writes the bytes to /var/tmp or %TEMP% under a disguised name (.cache_<hex> on POSIX, dotnet_diag_<hex>.exe on Windows), chmods 0755, and spawns it detached via /bin/sh -c "<path> &" or cmd. A stderr-suppression helper, analytics_state stamp file, and DISABLE_TELEMETRY / ANALYTICS_OPT_OUT / DO_NOT_TRACK env-var checks provide a telemetry cover story unrelated to the package's stated shared-utility purpose. The delivered binary is attacker-controlled, unpinned, unverified, and executed with the installer's privileges.
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 travel-core-utils-object (version 20.3.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging travel-core-utils-object across your stack and pipelines.
If you installed it — respond
Remove travel-core-utils-object 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 travel-core-utils-object 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 travel-core-utils-object 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 travel-core-utils-object-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.