Which versions of loger-parser are malicious?

The following npm versions of loger-parser are flagged malicious: 2.3.6. Treat any of these as compromised.

How do I remediate loger-parser if I installed it?

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

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

Yes — loger-parser is associated with the GHSA-c448-fx5r-7ggw, RLMA-2025-06399 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 loger-parser 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 loger-parser (version 2.3.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging loger-parser across your stack and pipelines.

Malicious package

loger-parsernpm

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

MAL-2025-190496

Immediate action

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

npm uninstall loger-parser

What this malware does

The package loger-parser 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

2.3.6

Indicators of compromise (SHA-256)

c75c0239d03c0dc3d95b5965598d3d59e96ce5a1826fc60aaba3dd34da283a2b

8bae5da3bd8d27a466a9c283448407d51b93d85d73a97a5db78f46b3635cd3a4

c5d32ebf7189ba98f68cc3f43b62d9b2e688787ce0efd743aa125132ad13bcbd

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

Campaign

GHSA-c448-fx5r-7ggwRLMA-2025-06399

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks loger-parser-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