Which versions of @zaka13/thing are malicious?

The following npm versions of @zaka13/thing are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @zaka13/thing if I installed it?

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.

I already installed @zaka13/thing — how do I know if it already compromised me?

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

Is @zaka13/thing part of a known attack campaign?

Yes — @zaka13/thing is associated with the GHSA-fxc7-fpjq-q7vf campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @zaka13/thing across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @zaka13/thing (version 1.0.0).

Malicious package

@zaka13/thingnpm

Advisory published Sep 14, 2026Updated Sep 30, 2026

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

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

1.0.0

Indicators of compromise (SHA-256)

d66d0b210651cf4c7b2b73a5cb399a972e1eeb86b822dba4ca1b0f98975a23c5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @zaka13/thing (version 1.0.0).
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.
Did it already run?
If @zaka13/thing 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. @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.

Campaign

GHSA-fxc7-fpjq-q7vf

References

github.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database