Which versions of supply_chain_dummy_test_2 are malicious?

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

How do I remediate supply_chain_dummy_test_2 if I installed it?

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

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

Yes — supply_chain_dummy_test_2 is associated with the GHSA-6rjq-vggp-p672, RLMA-2026-01600 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_2 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_2 (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 supply_chain_dummy_test_2 across your stack and pipelines.

Malicious package

supply_chain_dummy_test_2npm

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

MAL-2025-192761

Immediate action

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

npm uninstall supply_chain_dummy_test_2

What this malware does

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c6b93e13834edff34c14f85ca13ef5d5be2307f17c53ed7bf033a80d4f36f3b5

ed3f5fef388376bf388c291f40ce96d8431d31f38fb29b6f69b6543408d9ef2f

9bc8fe919adf841c92c2c305870d79de0cec8a1b375dd7ad077c6161ab330645

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_2 (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 supply_chain_dummy_test_2 across your stack and pipelines.
If you installed it — respond
Remove supply_chain_dummy_test_2 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_2 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_2 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_2 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

GHSA-6rjq-vggp-p672RLMA-2026-01600

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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