Which versions of researchpoc2 are malicious?

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

How do I remediate researchpoc2 if I installed it?

researchpoc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

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

Malicious package

researchpoc2npm

Malicious code in researchpoc2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-600

Immediate action

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

npm uninstall researchpoc2

What this malware does

The package researchpoc2 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)

f4dc24e7a14111cc2df68f08d7e66d1493e2c98b12d547140775f16bfe49f56c

543f158149a74f451a6b81f0c088ec8bcfbfb019477a57c17c44da8e58e2df3d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for researchpoc2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging researchpoc2 across your stack and pipelines.
If you installed it — respond
researchpoc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If researchpoc2 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 researchpoc2 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. researchpoc2 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-mq4c-jcxh-3w9f

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks researchpoc2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring