Which versions of viktorparserctf6 are malicious?

Every published version of viktorparserctf6 on npm is considered malicious. Remove the package entirely.

How do I remediate viktorparserctf6 if I installed it?

Remove viktorparserctf6 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed viktorparserctf6 — how do I know if it already compromised me?

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

Yes — viktorparserctf6 is associated with the GHSA-66gw-w3hf-7vw6 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 viktorparserctf6 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 viktorparserctf6 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging viktorparserctf6 across your stack and pipelines.

Malicious package

viktorparserctf6npm

viktorparserctf6 is a confirmed malicious npm package (MAL-2025-192652) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in viktorparserctf6 (npm)

MAL-2025-192652

Immediate action

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

npm uninstall viktorparserctf6

What this malware does

The package viktorparserctf6 was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

6893495a85291a71df39b5938c88e2a8aa526f0f35862bba004f7e184927de7f

6530edbf11d75d3f778f5f5f04cd6a3de4e0c38b99f88134dd4da0eee3bdb15b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for viktorparserctf6 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging viktorparserctf6 across your stack and pipelines.
If you installed it — respond
Remove viktorparserctf6 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If viktorparserctf6 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 viktorparserctf6 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. viktorparserctf6 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-66gw-w3hf-7vw6

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks viktorparserctf6-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database