Which versions of sql-limit-enforcer are malicious?

The following npm versions of sql-limit-enforcer are flagged malicious: 10.0.0. Treat any of these as compromised.

How do I remediate sql-limit-enforcer if I installed it?

sql-limit-enforcer establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed sql-limit-enforcer — how do I know if it already compromised me?

If sql-limit-enforcer 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.

Is sql-limit-enforcer part of a known attack campaign?

Yes — sql-limit-enforcer is associated with the IN-MAL-2026-020033 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find sql-limit-enforcer across my projects, lockfiles, and CI pipelines?

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

Malicious package

sql-limit-enforcernpm

sql-limit-enforcer is a confirmed malicious npm package (MAL-2026-16151) that opens a backdoor for remote access (malicious version 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sql-limit-enforcer (npm)

MAL-2026-16151

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall sql-limit-enforcer

What this malware does

Package ships no legitimate functionality: package.json declares main=index.js which is absent from the tarball, and the only shipped source is main.js, which runs from a postinstall hook (node main.js) during npm install. main.js collects host identifiers via require('os') — os.hostname(), os.userInfo(), os.platform(), os.arch(), process.cwd(), process.version — and POSTs them as JSON over https to the hardcoded collector URL https://webhook.site/13d98b4a-1999-4ec7-92c9-0697c259ca05. The declared purpose (SQL limit enforcer) is a cover; the artifact is an install-time reconnaissance beacon.

Malicious versions

1 flagged

10.0.0

Indicators of compromise (SHA-256)

6f8126bab8131e5781af023537f7c5fc2456929c104f71312eeddcea358b5659

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sql-limit-enforcer (version 10.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sql-limit-enforcer across your stack and pipelines.
If you installed it — respond
sql-limit-enforcer establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If sql-limit-enforcer 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.
How O3 protects you
O3 blocks sql-limit-enforcer 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-limit-enforcer on npm has been identified as a malicious package (version 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020033

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sql-limit-enforcer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database