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

statist-browser-typed-client-automlplatform.nlppl.searchynpm

Advisory published Updated

statist-browser-typed-client-automlplatform.nlppl.searchy is a confirmed malicious npm package (MAL-2026-12443) that executes malicious code on install (malicious version 20.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in statist-browser-typed-client-automlplatform.nlppl.searchy (npm)

MAL-2026-12443
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall statist-browser-typed-client-automlplatform.nlppl.searchy

What this malware does

On require() of this package, _init.js selects an OS/arch-specific endpoint from a list of Cloudflare Workers hostnames reconstructed at runtime via .join('') from split string fragments (e.g. ['oob-worker.cf100-416.w','ork','er','s.de','v'].join('')), downloads an opaque native binary via https.get, writes it to a temp path under a cover-story name (dotnet_diag_<hex>.exe / .cache_<hex>), chmods it 0755, and spawns it detached via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) (or spawn('cmd',...) on Windows). If HTTPS retrieval fails, the loader falls back to a DNS-TXT covert channel: dns.resolveTxt is called against tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site (also assembled from split fragments), and the TXT record contents are concatenated and base64-decoded to reconstruct the payload bytes. A checkStamp() flag file gates re-execution and stderr writes are used as silent no-op logs. The fetched binary is unpinned, unsigned, and unrelated to the package's advertised SDK purpose.

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

1 flagged
20.2.2

Indicators of compromise (SHA-256)

2006c1fa3443455515f9bbabd8bb63161c14be32405d601e0925054c02c0e62e
74e0f2d1d48f0a7879ceb5f476c7b45f9699402fecaa46060ee1cf06b09bf197

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for statist-browser-typed-client-automlplatform.nlppl.searchy (version 20.2.2).

  2. If you installed it — respond

    Remove statist-browser-typed-client-automlplatform.nlppl.searchy 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 statist-browser-typed-client-automlplatform.nlppl.searchy 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. statist-browser-typed-client-automlplatform.nlppl.searchy on npm has been identified as a malicious package (version 20.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014691GHSA-w6p7-7c73-jqc9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks statist-browser-typed-client-automlplatform.nlppl.searchy-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

statist-browser-typed-client-automlplatform.nlppl.searchy (npm) malicious package — MAL-2026-12443 | O3 Security