Which versions of technical-challenge are malicious?

The following npm versions of technical-challenge are flagged malicious: 1.0.1, 1.1.1. Treat any of these as compromised.

How do I remediate technical-challenge if I installed it?

technical-challenge 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 technical-challenge — how do I know if it already compromised me?

If technical-challenge 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 technical-challenge part of a known attack campaign?

Yes — technical-challenge is associated with the IN-MAL-2026-014935, GHSA-x874-j4r9-66gh, IN-MAL-2026-019792 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 technical-challenge 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 technical-challenge (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging technical-challenge across your stack and pipelines.

Malicious package

technical-challengenpm

technical-challenge is a confirmed malicious npm package (MAL-2026-12809) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in technical-challenge (npm)

MAL-2026-12809

Immediate action

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

npm uninstall technical-challenge

What this malware does

package.json declares preinstall: node index.js, causing index.js to run automatically on npm install. The script collects installer-side data — hostname, username, home directory, DNS server list, current working directory, package.json contents, and the contents of /etc/passwd and /etc/hosts — and HTTPS-POSTs it to a hardcoded Burp Collaborator subdomain at 5z5h9l8e7cktx1ihl6usn4zgb7h15rtg.oastify.com. The exfiltration fires unconditionally on install with no user interaction.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.11.1.1

Indicators of compromise (SHA-256)

6921f72a1b4fbaaba87fcbe3cb30137815e7e2bb932ffa794acd0010b8954c5f

fb3a6a289e12028cd0778c9ca9e56392a64003291be3756d28490d76c491e249

5c463733f8ad1a731f1c57442a70f944d04defbea213cba49d0f0c2dc52df85a

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

Campaign

IN-MAL-2026-014935GHSA-x874-j4r9-66ghIN-MAL-2026-019792

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks technical-challenge-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

Explore

All malware advisories How O3 detects malware Vulnerability database