Which versions of intquery are malicious?

The following npm versions of intquery are flagged malicious: 1.1.4, 1.1.5. Treat any of these as compromised.

How do I remediate intquery if I installed it?

Remove intquery 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.

I already installed intquery — how do I know if it already compromised me?

If intquery 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 intquery part of a known attack campaign?

Yes — intquery is associated with the GHSA-w7f8-x6ww-hf3x, IN-MAL-2026-008629, IN-MAL-2026-008628 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 intquery 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 intquery (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging intquery across your stack and pipelines.

Malicious package

intquerynpm

intquery is a confirmed malicious npm package (MAL-2026-6113) that executes malicious code on install (malicious versions 1.1.4, 1.1.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in intquery (npm)

MAL-2026-6113

Immediate action

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

npm uninstall intquery

What this malware does

[email protected] is published under the name 'intquery' by 'Stagnation Lab', but its README is a verbatim copy of the unrelated project ts-logger-pack (github.com/kallaspriit/ts-logger-pack) and its LICENSE attributes copyright to Priit Kallas. The README advertises 'A zero-dependency TypeScript logger interface', while package.json line 38 declares a runtime dependency on obfus-jsxy@^3.2.0 — a name with no relationship to logging and not mentioned anywhere in the README. The shipped dist/ contents are a trivial dummyLogger that does not use obfus-jsxy at runtime, so the dep serves no functional purpose for the advertised package. The structural pattern — identity-laundering (renamed clone, mismatched author/LICENSE/README), undeclared and purpose-mismatched runtime dep, trivial cover code — is the shape of a delivery vehicle that silently pulls obfus-jsxy onto any installer's machine via npm install intquery.

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

2 flagged

1.1.41.1.5

Indicators of compromise (SHA-256)

115c6fdd6b1a49aced7caf0b51b58290e6c07980e72cd7699dd360498a6790e5

cf4fe75f735c39be9ffe01686f69fd519c1408dd3473bb833506e1948fbc74a7

1d197b7ee4a4a4ba62531f3599f37e705106c4952381ed6c6ae0db15a53a850f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for intquery (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging intquery across your stack and pipelines.
If you installed it — respond
Remove intquery 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.
Did it already run?
If intquery 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 intquery 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. intquery on npm has been identified as a malicious package (versions 1.1.4, 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w7f8-x6ww-hf3xIN-MAL-2026-008629IN-MAL-2026-008628

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks intquery-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database