How do I remediate test1sharp if I installed it?

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

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

Yes — test1sharp is associated with the GHSA-89p7-jcpx-6x86, RLMA-2026-02048 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 test1sharp 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 test1sharp (24 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test1sharp across your stack and pipelines.

Malicious package

test1sharpnpm

Malicious code in test1sharp (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2250

Immediate action

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

npm uninstall test1sharp

What this malware does

The package test1sharp 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

24 flagged

0.34.50.35.50.35.60.36.60.36.70.36.80.36.90.37.00.37.20.37.30.37.40.37.50.37.60.37.70.37.80.37.90.38.00.38.10.38.20.38.30.38.50.38.60.38.70.38.8

Indicators of compromise (SHA-256)

c18dd124c0c097c8c6e277f7fd86c791a6d988ecb5545f5811c669e6c1269a95

870c745216e287e72f189910e8bd7369f6d6aedbabf85077bfe170b2d1e1de12

93a04151d166610e791fa400eae5fcb388fd0ffdf040e473cdffb4692632fa14

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 test1sharp (24 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test1sharp across your stack and pipelines.
If you installed it — respond
Remove test1sharp 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 test1sharp 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 test1sharp 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. test1sharp on npm has been identified as a malicious package (versions 0.34.5, 0.35.5, 0.35.6, 0.36.6, 0.36.7, 0.36.8, 0.36.9, 0.37.0, and 16 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-89p7-jcpx-6x86RLMA-2026-02048

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks test1sharp-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