Which versions of supply_chain_dummy_test_3 are malicious?

The following npm versions of supply_chain_dummy_test_3 are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate supply_chain_dummy_test_3 if I installed it?

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

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

Yes — supply_chain_dummy_test_3 is associated with the GHSA-r6g5-cgp3-h24c, RLMA-2026-01601 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 supply_chain_dummy_test_3 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 supply_chain_dummy_test_3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging supply_chain_dummy_test_3 across your stack and pipelines.

Malicious package

supply_chain_dummy_test_3npm

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

MAL-2025-192762

Immediate action

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

npm uninstall supply_chain_dummy_test_3

What this malware does

The package supply_chain_dummy_test_3 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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

a537a1124f235f17d73b1437e8a1bc9e453f10cdecd2fcf1adf70e5eca1e89f9

f1963b5503ceeb0e8ed806c386f27edc1761eab24549419a8911a00f525b4a4c

17e919f34aec0b3cf95504649fc2857916f6cc16888d55077a651dbce6c770c4

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

Campaign

GHSA-r6g5-cgp3-h24cRLMA-2026-01601

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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