> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/uncommon-node-js-package-initiated-communication-to-an-external-host.md).
# Uncommon Node.js package initiated communication to an external host
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent |
| Detector Tags | Malicious Packages Analytics |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.001) |
| Severity | Low |
### Description
An npm package executed by node.exe/bun.exe initiated an outbound connection to an external host that is rarely contacted by that package within the organization. Such abnormal connections can indicate supply-chain compromise (e.g. malicious postinstall scripts), but also command-and-control, data exfiltration, or other unexpected outbound activity.
### Attacker's Goals
Abuse an npm package executed by node.exe/bun.exe (e.g. via a malicious postinstall script) to establish command and control or exfiltrate data to a rarely-seen external host.
### Investigative actions
* Review the full command line used by the package.
* Check the reputation of the external destination host.
* Verify whether the npm package is legitimate and expected on the host.
### Variations
Uncommon Node.js package initiated communication to an external host reaching a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.001) |
| Severity | Low |
**Description**
An npm package executed by node.exe/bun.exe initiated an outbound connection to an external host that is rarely contacted by that package within the organization. Such abnormal connections can indicate supply-chain compromise (e.g. malicious postinstall scripts), but also command-and-control, data exfiltration, or other unexpected outbound activity.
**Attacker's Goals**
Abuse an npm package executed by node.exe/bun.exe (e.g. via a malicious postinstall script) to establish command and control or exfiltrate data to a rarely-seen external host.
**Investigative actions**
* Review the full command line used by the package.
* Check the reputation of the external destination host.
* Verify whether the npm package is legitimate and expected on the host.
Uncommon Node.js package initiated communication to an external host from a package with limited destination diversity
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.001) |
| Severity | Low |
**Description**
An npm package executed by node.exe/bun.exe initiated an outbound connection to an external host that is rarely contacted by that package within the organization. Such abnormal connections can indicate supply-chain compromise (e.g. malicious postinstall scripts), but also command-and-control, data exfiltration, or other unexpected outbound activity.
**Attacker's Goals**
Abuse an npm package executed by node.exe/bun.exe (e.g. via a malicious postinstall script) to establish command and control or exfiltrate data to a rarely-seen external host.
**Investigative actions**
* Review the full command line used by the package.
* Check the reputation of the external destination host.
* Verify whether the npm package is legitimate and expected on the host.
Uncommon Node.js package initiated communication to an external host over HTTP on a non-standard port
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Supply Chain Compromise: Compromise Software Dependencies and Development Tools (T1195.001) |
| Severity | Low |
**Description**
An npm package executed by node.exe/bun.exe initiated an outbound connection to an external host that is rarely contacted by that package within the organization. Such abnormal connections can indicate supply-chain compromise (e.g. malicious postinstall scripts), but also command-and-control, data exfiltration, or other unexpected outbound activity.
**Attacker's Goals**
Abuse an npm package executed by node.exe/bun.exe (e.g. via a malicious postinstall script) to establish command and control or exfiltrate data to a rarely-seen external host.
**Investigative actions**
* Review the full command line used by the package.
* Check the reputation of the external destination host.
* Verify whether the npm package is legitimate and expected on the host.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/uncommon-node-js-package-initiated-communication-to-an-external-host.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.