@khaznatech/common
KhaznaTech shared common utilities for Node.js services
This report shows the evidence for @khaznatech/common@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 performs unconsented, install-time transmission of host and installation-context data to an unrelated webhook endpoint. Its normal runtime entrypoint is benign, but the lifecycle behavior is a concrete exfiltration chain.
Decision evidence
public snapshot- npm preinstall executes install-report.js automatically.
- Install script sends hostname and install-directory name to a webhook.site URL.
- Errors are swallowed, obscuring the outbound telemetry.
- index.js contains only local utility helpers.
- No credential, shell, file-write, or remote-code execution behavior found.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgnpm preinstall executes install-report.js automatically.
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/common@99.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @khaznatech/common@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.