MAL-2026-20271: Malicious code in smfos-bskdz-util (npm)

Published Nov 20, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (ec58aa63a556255a6052491e8d50ff5f9e44d58f32044028f3f1ae978789e0c0) 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.

Affected Software

1 affected component
npm/smfos-bskdz-util*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove npm/smfos-bskdz-util from your environment.

    Remove the smfos-bskdz-util package.

  2. Operational

    Rotate all secrets and keys stored on the affected computer immediately, using a different computer.

Event History

Nov 20, 2026
Advisory Published
via OSV·01:02 AM
Data Sourced
via OSV·01:02 AM
DescriptionAffected Software

Frequently Asked Questions

1

When does the malicious code execute?

It executes when the package is required or imported. Its index.js decodes a byte array from the package manifest and passes the result to the Function constructor with access to require and __dirname.

2

What access could the package's code obtain?

The dynamic code runs with access to require and the installing project's directory. The advisory states that any computer with the package installed or running should be treated as fully compromised.

3

Are systems using version 1.0.1 known to have executed a harmful payload?

In version 1.0.1, the decoded payload resolves to console.log(1). However, the obfuscated import-time execution mechanism allows a future published version to run arbitrary author-controlled code.

4

What should be done if this package is present?

Treat the affected computer as fully compromised and rotate all secrets and keys stored on it immediately.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203