Which versions of magic-poc are malicious?

The following npm versions of magic-poc are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate magic-poc if I installed it?

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

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

Yes — magic-poc is associated with the GHSA-m6v9-f3q8-q9qj 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 magic-poc 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 magic-poc (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging magic-poc across your stack and pipelines.

Malicious package

magic-pocnpm

Malicious code in magic-poc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192939

Immediate action

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

npm uninstall magic-poc

What this malware does

The package magic-poc 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.

The OpenSSF Package Analysis project identified 'magic-poc' @ 0.1.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

dc07633fe576722d0fb4d3e2f9c60c09d23564789e3b78dc0f6ed3c3d371da65

6dea39f25cc72cc9ab080d6f35ef68c9a061a8df5fe184194798109dad36faa5

89ec0cb0d10ed48f38fd79d080a40f46510b46211da23e64a2c72d9b053cb73b

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

Campaign

GHSA-m6v9-f3q8-q9qj

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks magic-poc-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