Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@zaka13/thingnpm

@zaka13/thing is a confirmed malicious npm package (MAL-2026-16200) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zaka13/thing (npm)

MAL-2026-16200
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @zaka13/thing

What this malware does

@zaka13/[email protected] ships the same disguised in-browser proxy kit as webpackbootstrap5 and webpackbootstrapscripts by the same publisher (zaka13). Its YXBp.js loader matches those packages' index-z2b7r4.js (same sha256): it XOR-decodes endpoints with a fixed key, injects remote scripts from https://dyingefforlessefforlessours.com, and boots a Scramjet/wisp WebSocket proxy routing traffic through operator relays. The package presents itself as 'thingy' with an SVG main entry. Harm is browser-side when the asset is served; no install script runs.

Malicious versions

1 flagged
1.0.0

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @zaka13/thing (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zaka13/thing across your stack and pipelines.

  2. If you installed it — respond

    Remove @zaka13/thing 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 @zaka13/thing 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.

  4. How O3 protects you

    O3 blocks @zaka13/thing 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

No. @zaka13/thing on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • pkgwarden · finder

Detect & block this

O3 blocks @zaka13/thing-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

@zaka13/thing (npm) malicious package — MAL-2026-16200 | O3 Security