Which versions of my-ctf-helper-script-9921 are malicious?

The following npm versions of my-ctf-helper-script-9921 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate my-ctf-helper-script-9921 if I installed it?

my-ctf-helper-script-9921 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 my-ctf-helper-script-9921 — how do I know if it already compromised me?

If my-ctf-helper-script-9921 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 my-ctf-helper-script-9921 part of a known attack campaign?

Yes — my-ctf-helper-script-9921 is associated with the IN-MAL-2026-020273 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 my-ctf-helper-script-9921 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 my-ctf-helper-script-9921 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging my-ctf-helper-script-9921 across your stack and pipelines.

Malicious package

my-ctf-helper-script-9921npm

my-ctf-helper-script-9921 is a confirmed malicious npm package (MAL-2026-16365) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in my-ctf-helper-script-9921 (npm)

MAL-2026-16365

Immediate action

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

npm uninstall my-ctf-helper-script-9921

What this malware does

On require/import, the package's main module executes a top-level fetch to the hardcoded collector URL https://webhook.site/99e9df7b-fe86-4c60-822a-5352b1f9edf0/, appending document.cookie as a query-string parameter. The package has no other advertised functionality; the sole effect of loading it is to send the ambient cookie value to a third-party webhook capture endpoint controlled by whoever provisioned that webhook.site token. webhook.site is a generic ad-hoc data-collection service, unrelated to any legitimate publisher infrastructure.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

41ee1dafe6dce8750ac695c9d13e13c2808e2f35d94bbbcc41a4444a02541409

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

Campaign

IN-MAL-2026-020273

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks my-ctf-helper-script-9921-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