Which versions of nemo-reporter are malicious?

The following npm versions of nemo-reporter are flagged malicious: 1.8.3. Treat any of these as compromised.

How do I remediate nemo-reporter if I installed it?

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

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

Yes — nemo-reporter is associated with the GHSA-358g-x45v-57vw 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 nemo-reporter 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 nemo-reporter (version 1.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nemo-reporter across your stack and pipelines.

Malicious package

nemo-reporternpm

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

MAL-2026-4836

Immediate action

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

npm uninstall nemo-reporter

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.

The OpenSSF Package Analysis project identified 'nemo-reporter' @ 1.8.3 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.8.3

Indicators of compromise (SHA-256)

6a4b651421d56ff7c35f6192795f0eb27038df786c20f2d585703229f5007952

42a43ec0a345170ad191fa1c25bdd4000595aa8ce733c6b9c69de6b65a1defb2

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

Campaign

GHSA-358g-x45v-57vw

References

github.com

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks nemo-reporter-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