Which versions of @jameson777/mytest5 are malicious?

The following npm versions of @jameson777/mytest5 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @jameson777/mytest5 if I installed it?

Remove @jameson777/mytest5 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 @jameson777/mytest5 — how do I know if it already compromised me?

If @jameson777/mytest5 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 @jameson777/mytest5 part of a known attack campaign?

Yes — @jameson777/mytest5 is associated with the GHSA-p845-h89c-g88c, RLMA-2025-05659 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 @jameson777/mytest5 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 @jameson777/mytest5 (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 @jameson777/mytest5 across your stack and pipelines.

Malicious package

@jameson777/mytest5npm

@jameson777/mytest5 is a confirmed malicious npm package (MAL-2025-48919) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @jameson777/mytest5 (npm)

MAL-2025-48919

Immediate action

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

npm uninstall @jameson777/mytest5

What this malware does

The package @jameson777/mytest5 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)

10445c0fd7f9820fa2cbd31fb53b2d2fc7bd4559c2f341f06b1c8973c0b94238

4bfcd1d23e28023307b1ce65b03a678a6b989b630795691e92b2d0a1fc7c7f99

627ddfeff4c847989e5487711230cc4a9e7bd10cc939624e9e20da8cd7c9ea2f

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 @jameson777/mytest5 (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 @jameson777/mytest5 across your stack and pipelines.
If you installed it — respond
Remove @jameson777/mytest5 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 @jameson777/mytest5 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 @jameson777/mytest5 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. @jameson777/mytest5 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-p845-h89c-g88cRLMA-2025-05659

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @jameson777/mytest5-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