Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@sql-trigger/nodesqlnpm

Malicious code in @sql-trigger/nodesql (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5395
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sql-trigger/nodesql

What this malware does

The package advertises itself as a simple SQL helper but its main entry index.js is heavily obfuscated (obfuscator.io string-array + RC4 + base64, 218-entry shuffled literal array, two RC4 decoders) with no human-readable logic. After deobfuscation, the top-level IIFE requires os/fs/path/child_process/axios, installs uncaughtException and unhandledRejection handlers to suppress errors, then assembles an IPv4 address at runtime by concatenating four numeric octets with '.', issues an axios HTTP GET to that host, writes the response body into os.tmpdir() with flag 'w+', and invokes child_process exec/spawn on the written file with windowsHide:true and cwd set to the tmp directory. This is a generic remote-binary dropper: the destination is mutable, the payload is opaque and unverified, the URL is built at runtime to evade static scanners, and the fetched file is unrelated to any SQL functionality. The dropper fires the moment any consumer require()s the package, so installing this dependency results in attacker-controlled code being downloaded to and executed from the consumer's temp directory.

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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

39e37d95fb040c83277583e2bf90b56363f86360337f1c30e63c85eb56579ada
df686aa903ce47ad4414266558600486e522e7ad0bf4e5876018ef24bca1d1a3
af206fa9674f6676548fa54503b38eaa9a0cd31b267e4b7a39598bfde93c0e54
726694fd8558bf7ac804c1e9805a693864d69ec7f8194c1f271b7adf1b721c26

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sql-trigger/nodesql (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sql-trigger/nodesql across your stack and pipelines.

  2. If you installed it — respond

    Remove @sql-trigger/nodesql 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 @sql-trigger/nodesql was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @sql-trigger/nodesql before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @sql-trigger/nodesql on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004942IN-MAL-2026-006142GHSA-9f9w-wg5j-m53jIN-MAL-2026-009252

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @sql-trigger/nodesql-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.