accounts-limitsnpm
accounts-limits is a confirmed malicious npm package (MAL-2026-12134) that executes malicious code on install (malicious versions 0.0.2, 33.6.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in accounts-limits (npm)
What this malware does
index.js unconditionally requires./runtime.js, which on module load selects a per-platform asset path, fetches an opaque binary from one of three Cloudflare Workers hosts (oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT chunked base64 fallback under *.dl.well1.site, writes the bytes to /tmp or the Windows TEMP directory under benign-looking names (.cache<hex>, dotnet_diag_<hex>.exe,.analytics_state), chmods the file 0755, and detached-spawns it via spawn('/bin/sh',...) or spawn('cmd',...). No hash or signature verification is performed and the fetched payload is unrelated to the stated 'accounts limits' purpose. Both the primary Workers hosts and DNS fallback domains are assembled at runtime by join()ing fragmented substrings (e.g. ['tin.dl.w','ell','1.site'].join(''), ['oob-worker.cf100-4','16','.workers.de','v'].join('')), and stderr is stubbed via _l() to suppress diagnostics. A second dropper at lib/telemetry.js (81KB, presented as an 'analytics SDK') duplicates the chmod-and-spawn pattern with cp.spawn('/bin/sh',['-c', filePath+' &']) and base64-decoded buffer writes; it is staged in the tarball but not currently on the require-chain from index.js.
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 accounts-limits (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging accounts-limits across your stack and pipelines.
If you installed it — respond
Remove accounts-limits 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 accounts-limits 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 accounts-limits 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 accounts-limits-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.