lifestyle-test-utilsnpm
Advisory published Updated
lifestyle-test-utils is a confirmed malicious npm package (MAL-2026-11514) that executes malicious code on install (malicious version 20.7.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lifestyle-test-utils (npm)
What this malware does
On require() of lifestyle-test-utils, index.js loads ext.js which selects a platform-specific asset, downloads a binary from one of three Cloudflare Workers hosts whose names are assembled by runtime string-concatenation (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked base64 fallback resolver under *.dl.well1.site, writes the payload to /var/tmp or %TEMP% under disguised names (.cache<hex>, dotnet_diag_<hex>.exe), chmods it 0755, and spawns it detached via /bin/sh -c or cmd. There is no hash or signature verification. Endpoint hostnames are fragmented and reassembled at runtime to evade plain-text scanning. Execution is gated by DISABLE_TELEMETRY/ANALYTICS_OPT_OUT/DO_NOT_TRACK env checks and a ~5.5 hour re-run stamp file framed as 'analytics_state', a cover story unrelated to the package's stated 'common helpers' purpose. The result is arbitrary attacker-controlled code execution on any host that installs or requires this package.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for lifestyle-test-utils (version 20.7.2).
If you installed it — respond
Remove lifestyle-test-utils 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 lifestyle-test-utils was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks lifestyle-test-utils-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.