Which versions of search-connector-template are malicious?

The following npm versions of search-connector-template are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate search-connector-template if I installed it?

search-connector-template 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 search-connector-template — how do I know if it already compromised me?

If search-connector-template 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 search-connector-template part of a known attack campaign?

Yes — search-connector-template is associated with the IN-MAL-2026-004028, IN-MAL-2026-004029 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 search-connector-template 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 search-connector-template (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging search-connector-template across your stack and pipelines.

Malicious package

search-connector-templatenpm

Malicious code in search-connector-template (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4664

Immediate action

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

npm uninstall search-connector-template

What this malware does

package.json declares preinstall: node index.js, which fires automatically on npm install. index.js collects host identity (hostname, username, homedir, DNS servers) and reads installer-owned system files (/etc/passwd, /etc/hosts), then POSTs the JSON payload over HTTPS to a Burp Collaborator OAST subdomain (615arnt4a5f6ii011q8kggqfk6q1er2g.oastify.com). This is a classic install-time exfiltration beacon: the destination is attacker-controlled, the data leaving the host belongs to the installer rather than the package author, and execution requires no user action beyond running npm install.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

24aea8e5a7338c49dc96e3945ed4d695024c2e169f560e6f3426005ca4666ea4

a3b0d5dda5e0170aec1d5dca46e941693ed27c658a8248cc91ad3f44c73b4fec

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 search-connector-template (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging search-connector-template across your stack and pipelines.
If you installed it — respond
search-connector-template 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 search-connector-template 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 search-connector-template 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. search-connector-template on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004028IN-MAL-2026-004029

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks search-connector-template-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