@khaznatech/core
KhaznaTech shared core utilities for Node.js services
This report shows the evidence for @khaznatech/core@99.0.0, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package’s preinstall hook performs a concrete, automatic outbound collection of host and installation metadata to a third-party webhook. The normal runtime entrypoint does not mitigate that install-time behavior.
Decision evidence
public snapshot- package.json runs install-report.js during npm preinstall.
- install-report.js sends hostname and install-directory name to a third-party webhook during installation.
- The request is error-swallowed, reducing visibility of the install-time telemetry.
- index.js contains only small local utility exports.
- No source evidence of file writes, shell execution, or remote payload execution.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs install-report.js during npm preinstall.
package.jsonView on unpkg · L6Source fingerprint signature matches a known malicious package signature; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @khaznatech/core@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @khaznatech/core@99.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.