This report shows the evidence for smfos-bskdz-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-20271 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as clean; 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-20271 confirms this npm version as malicious.
Advisory
MAL-2026-20271
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in smfos-bskdz-util (npm)
Details
On require, index.js reads a numeric byte array from a non-standard `_b` field in package.json, XORs each byte with 0x96, and passes the result to the Function constructor along with `require` and `__dirname`. In version 1.0.1 the decoded bytes resolve to a trivial `console.log(1)`, but the package exports an empty object and advertises itself as a utility, so the only functional behavior shipped is this dynamic-execution channel. The payload is stored in a manifest field under a single-letter key, outside any shipped.js source, and is only reachable through the XOR transform — a deliberate obfuscation shape that lets any future published version execute arbitrary author-controlled code at import time with full access to `require` and the installing project's directory.
## Source: ghsa-malware (f15455f24cd57ac6b7bdd0de11c511ba1ce862fd870c2bdad19f93f67cc34b45) 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 clean. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The entry point uses obfuscation and dynamic evaluation at import time, but decoding the embedded bytes shows only console.log(1). No harmful actions or network activity were identified.
Static reason
No blocking static signals were detected.
Trigger
Importing the package through its index.js entry point.
Impact
A console message during import; no harmful behavior was identified.
Mechanism
index.js XORs bytes from package.json with 0x96 and evaluates the resulting text with the Function constructor; the decoded text is console.log(1).
Independent scan evidence
public snapshot
AI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
The package entry point is index.js.
At import time, index.js XOR-decodes bytes from package.json and evaluates the result using the Function constructor.
The decoded text is console.log(1); the entry point then exports an empty object.
Evidence against
The import-time dynamic evaluation is obscured by XOR-encoded bytes.
The package does not expose useful behavior beyond the import-time console output.
Behavioral surface
SourceNo risky source behavior triggered.
Supply chainTrivial
ManifestNo manifest risk signals triggered.
Scanned 1 file · 316 B of source
Findings
5 high
Where they are, most severe file 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 smfos-bskdz-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.