Which versions of @khaznatech/common are malicious?

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

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

@khaznatech/common is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @khaznatech/common — how do I know if it already compromised me?

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

Yes — @khaznatech/common is associated with the IN-MAL-2026-017688 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/common 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/common (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/common across your stack and pipelines.

Malicious package

@khaznatech/commonnpm

@khaznatech/common is a confirmed malicious npm package (MAL-2026-13973) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @khaznatech/common (npm)

MAL-2026-13973

Immediate action

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

npm uninstall @khaznatech/common

What this malware does

The package's preinstall script (install-report.js) runs automatically on npm install and performs an HTTPS GET to a hardcoded webhook.site capture endpoint, appending the installer's hostname (os.hostname()) and current working directory basename (process.cwd()) to the URL path. webhook.site is an anonymous third-party request-capture service, not publisher infrastructure, and the exfiltrated values identify the installer's machine and project. The behavior is labeled as install telemetry in a comment but is not disclosed, not opt-in, and directed at an anonymous endpoint rather than a package-owned or caller-configured destination.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

59ac302f60b532a4e864c576593db300a20abba96ae2a53ba5da0cc06d8dc911

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @khaznatech/common (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/common across your stack and pipelines.
If you installed it — respond
@khaznatech/common is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @khaznatech/common 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/common 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/common 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-017688

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @khaznatech/common-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database