NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

accounts-limitsnpm

Advisory published Updated

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)

MAL-2026-12134
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall accounts-limits

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

2 flagged
0.0.233.6.6

Indicators of compromise (SHA-256)

69c43a5fbac213b36e4a3d7c25d7f41311e6f3f111f3b175e2f306077afbcde0
f213229f671ddeca9cae21feab6f9eb0bbd3b88743b8af6dbea340a2a609adbe

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for accounts-limits (2 malicious versions).

  2. 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.

  3. Did it already run?

    If accounts-limits 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

No. accounts-limits on npm has been identified as a malicious package (versions 0.0.2, 33.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014553IN-MAL-2026-014548

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.

Explore

accounts-limits (npm) malicious package — MAL-2026-12134 | O3 Security