Which versions of internal-checkout-bricks are malicious?

The following npm versions of internal-checkout-bricks are flagged malicious: 99.0.0, 99.49.53. Treat any of these as compromised.

How do I remediate internal-checkout-bricks if I installed it?

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

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

Yes — internal-checkout-bricks is associated with the GHSA-22w9-rm4j-69f9, RLMA-2025-05393, RLUA-2025-05815 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 internal-checkout-bricks 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 internal-checkout-bricks (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging internal-checkout-bricks across your stack and pipelines.

Malicious package

internal-checkout-bricksnpm

internal-checkout-bricks is a confirmed malicious npm package (MAL-2025-48283) that executes malicious code on install (malicious versions 99.0.0, 99.49.53). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internal-checkout-bricks (npm)

MAL-2025-48283

Immediate action

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

npm uninstall internal-checkout-bricks

What this malware does

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

99.0.099.49.53

Indicators of compromise (SHA-256)

a7a30a0c50c357c109e976dd834294a7f9414d5d0589e68deea9385dcdb6dff7

0cf6d600ee2e735dfff05da4c276557256e5603151c11ee64d81d5c97578d484

9410f996309371b775ce7b10e68690c73826433c17e7fe56eb27927972af5206

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

Campaign

GHSA-22w9-rm4j-69f9RLMA-2025-05393RLUA-2025-05815

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks internal-checkout-bricks-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