Which versions of @jameson777/mytest6 are malicious?

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

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

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

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

Yes — @jameson777/mytest6 is associated with the GHSA-pxpv-4grp-crc8, RLMA-2025-05660 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/mytest6 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/mytest6 (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/mytest6 across your stack and pipelines.

Malicious package

@jameson777/mytest6npm

@jameson777/mytest6 is a confirmed malicious npm package (MAL-2025-48920) 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/mytest6 (npm)

MAL-2025-48920

Immediate action

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

npm uninstall @jameson777/mytest6

What this malware does

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

a38e525403f1e7301c1943f6ef57dc285a615590bb381e42682e609cc5fa786f

851f11df6052c000d2359d23f1429e77a60896e9f279467656eedf7c968cdf07

1b81301cbdeeb3c065c93597e415f4e2ed5e2bb7a6cf965a442a7fbbd6a47533

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/mytest6 (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/mytest6 across your stack and pipelines.
If you installed it — respond
Remove @jameson777/mytest6 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/mytest6 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/mytest6 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/mytest6 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-pxpv-4grp-crc8RLMA-2025-05660

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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