Which versions of @khaznatech/core are malicious?

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

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

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

If @khaznatech/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @khaznatech/core part of a known attack campaign?

Yes — @khaznatech/core is associated with the IN-MAL-2026-017686 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/core across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @khaznatech/core (version 99.0.0).

Malicious package

@khaznatech/corenpm

Advisory published Aug 13, 2026Updated Aug 13, 2026

@khaznatech/core is a confirmed malicious npm package (MAL-2026-13974) that opens a backdoor for remote access (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @khaznatech/core (npm)

MAL-2026-13974

Immediate action

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

npm uninstall @khaznatech/core

What this malware does

The package ships install-report.js as a preinstall lifecycle script that unconditionally runs on npm install. The script reads os.hostname() and the current working directory basename and transmits them via https.get to a hardcoded third-party collector at https://webhook.site/93b065ab-227f-4253-b940-361d00e9b870/, appending the host identifiers as the URL path. The destination is an anonymous request-inspection endpoint unrelated to any declared package purpose, and the beacon fires silently on every installation without opt-in.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

820c7f4f32895ef501e6926f624897cf41b5f868bc21c60852cbfc101b4cd5ba

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @khaznatech/core (version 99.0.0).
If you installed it — respond
@khaznatech/core 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 @khaznatech/core was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @khaznatech/core 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-017686

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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