Which versions of myreviews-core are malicious?

The following npm versions of myreviews-core are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate myreviews-core if I installed it?

myreviews-core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed myreviews-core — how do I know if it already compromised me?

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

Yes — myreviews-core is associated with the IN-MAL-2026-010725 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 myreviews-core 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 myreviews-core (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging myreviews-core across your stack and pipelines.

Malicious package

myreviews-corenpm

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

MAL-2026-10740

Immediate action

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

npm uninstall myreviews-core

What this malware does

package.json declares a postinstall lifecycle hook that runs node -e to issue an HTTPS GET to a hardcoded webhook.site collector URL, appending the installer's hostname (os.hostname()), OS username (os.userInfo().username), current working directory (process.cwd()), and a timestamp as query parameters. The request fires automatically on npm install with no opt-in and no relation to any documented package functionality. The version number (99.0.0) is consistent with a dependency-confusion lure intended to shadow an internal package name and beacon successful installs to the attacker.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

9c41d5d4352e265f0efbc0089a19c5773ceeb76c0265831eeeeca19151fe4f64

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for myreviews-core (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging myreviews-core across your stack and pipelines.
If you installed it — respond
myreviews-core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If myreviews-core 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 myreviews-core 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. myreviews-core on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010725

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks myreviews-core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring