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

prism-silqnpm

Advisory published Updated

prism-silq is a confirmed malicious npm package (MAL-2026-6493) 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 prism-silq (npm)

MAL-2026-6493
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall prism-silq

What this malware does

The package ships a binding.gyp whose sources field uses GYP command-expansion syntax (<!(...)) at line 6. npm implicitly runs node-gyp rebuild whenever a binding.gyp is present, even without a declared install/postinstall script, and GYP evaluates <!(...) as a shell command during the configure step. This causes the embedded command to run automatically on every npm install, equivalent to a lifecycle hook executing attacker-controlled code on the installer's machine. This pattern abuses the native-addon build system to gain silent install-time code execution, and is not a legitimate native-extension build configuration.

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)

6bb3e8b0ded57991e21f137aac7c905348a83f6be7914c4da619c18d2acd280c
74ab07f46075a5eb20bc767057eff7449e06423dea9a627b050c07e732ae0f6b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for prism-silq (version 1.0.1).

  2. If you installed it — respond

    Remove prism-silq 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 prism-silq 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. prism-silq 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-007573GHSA-6hp6-2792-v6q5

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks prism-silq-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

prism-silq (npm) malicious package — MAL-2026-6493 | O3 Security