Which versions of @khaznatech/utils are malicious?

The following npm versions of @khaznatech/utils are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @khaznatech/utils if I installed it?

Remove @khaznatech/utils 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 @khaznatech/utils — how do I know if it already compromised me?

If @khaznatech/utils 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 @khaznatech/utils part of a known attack campaign?

Yes — @khaznatech/utils is associated with the IN-MAL-2026-017687 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 @khaznatech/utils 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 @khaznatech/utils (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @khaznatech/utils across your stack and pipelines.

Malicious package

@khaznatech/utilsnpm

@khaznatech/utils is a confirmed malicious npm package (MAL-2026-13975) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @khaznatech/utils (npm)

MAL-2026-13975

Immediate action

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

npm uninstall @khaznatech/utils

What this malware does

The package declares a preinstall script (install-report.js) that runs on npm install. It reads os.hostname() and the current working directory basename and sends them via https.get to a hardcoded webhook.site inbox (https://webhook.site/93b065ab-227f-4253-b940-361d00e9b870/). webhook.site is an anonymous request-inspection service that has no relation to the package's stated utilities purpose. The scoped name @khaznatech/utils combined with the unusually high version number 99.0.0 is consistent with a dependency-confusion probe designed to identify internal build systems that resolve the public name over a private one.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

3d6d321090b3f66b7766ca73a5cebf1a2d3ab2908d8d31f8423616c8094ec0a8

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 @khaznatech/utils (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @khaznatech/utils across your stack and pipelines.
If you installed it — respond
Remove @khaznatech/utils 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 @khaznatech/utils 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 @khaznatech/utils 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. @khaznatech/utils on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017687

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @khaznatech/utils-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