This report shows the evidence for tsbwt-hawsi-util@1.0.1. 1 of 4 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20272 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20272 confirms this npm version as malicious.
Advisory
MAL-2026-20272
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in tsbwt-hawsi-util (npm)
Details
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.
## Source: ghsa-malware (f60d2fd5582018d3f424ae73b45ab0e09876546e79056ae4de67d2be71b29cf9) 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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package executes an obscured payload automatically when imported, which is unrelated to its stated utility purpose. The decoded payload only logs 1, so the evidence supports a warning for unexplained obfuscated behavior rather than a malicious verdict.
Static reason
No blocking static signals were detected.
Trigger
Importing the package through its main entry, index.js.
Impact
An unexplained console output occurs on import; no further impact was identified.
Mechanism
index.js inflates the `_bz` array from package.json and passes the decoded text to a dynamically constructed function; the payload logs `1`.
Evidence
index.jspackage.json
Independent scan evidence
public snapshot
AI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for AI warning decision
Importing the main entry inflates data from package.json and executes it through a dynamically constructed function.
The hidden payload decodes to `console.log(1)`, an unexplained import-time side effect for a package described only as a utility.
Evidence against
The decoded payload only logs `1`; no harmful action was identified.
The inspected source shows no network endpoint or file operation.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 269 B of source
Findings
2 high
Most severe first. Code opens a file's flagged lines, with their evidence, below.
The versions list below shows the verdict for each recorded version.
Avoid installing tsbwt-hawsi-util@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.