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

fs-commonsnpm

Advisory published Updated

fs-commons is a confirmed malicious npm package (MAL-2026-17301) 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 fs-commons (npm)

MAL-2026-17301
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fs-commons

What this malware does

The package presents itself as a filesystem/data-helper library, but its exported getTransactions()/load_transaction_data() functions are a two-file dynamic-code loader. index.js hides the identifiers 'Function', 'require', 'process', 'Buffer', and 'setTimeout' behind a split-string array and obtains the Function constructor indirectly via globalThis.constructor.constructor, defeating static review. At call time it reads the sibling file models.js, which is disguised as an array of product-record objects but whose mark fields are base64 ciphertext. loadConfig()/processData() sort the records by id, concatenate every mark, apply a per-count Caesar shift, base64-decode the result, and pass the resulting source to the Function constructor with Buffer, require, and process injected, then invoke it. Any consumer that requires fs-commons and calls getTransactions() executes attacker-supplied code with full Node privileges on the host process. The obfuscation, the indirect Function-constructor acquisition, and the disguising of the payload as product metadata in a sibling file have no legitimate purpose for a data-helper library and are the fingerprint of a supply-chain remote-code-execution package.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

f7e82e98343807c39ea786017de4d2a7455815424155ca2a856333d895c8a48b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for fs-commons (version 1.0.1).

  2. If you installed it — respond

    Remove fs-commons 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 fs-commons 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. fs-commons 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

IN-MAL-2026-020698

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks fs-commons-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

fs-commons (npm) malicious package — MAL-2026-17301 | O3 Security