Which versions of sheratan_test_p are malicious?

The following npm versions of sheratan_test_p are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate sheratan_test_p if I installed it?

sheratan_test_p is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed sheratan_test_p — how do I know if it already compromised me?

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

Yes — sheratan_test_p is associated with the IN-MAL-2026-006877 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 sheratan_test_p 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 sheratan_test_p (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 sheratan_test_p across your stack and pipelines.

Malicious package

sheratan_test_pnpm

sheratan_test_p is a confirmed malicious npm package (MAL-2026-5993) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sheratan_test_p (npm)

MAL-2026-5993

Immediate action

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

npm uninstall sheratan_test_p

What this malware does

On npm install, the package's postinstall.js executes whoami via child_process and POSTs the output (along with stderr, error, and a timestamp) to a hardcoded webhook.site collector URL. The package self-describes as 'A simple date formatting utility' and contains no code matching that purpose; the only behavior on install is the host-identity beacon. Package metadata is consistent with a throwaway exfiltration artifact (placeholder name sheratan_test_p, empty author, generic description). Any developer or CI runner installing this package leaks their user/host context to an attacker-controlled third-party collector.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

472354ac3cd0bba5d399eea2f09e4b7f60cb2cb65e20d4af0f6398882403f566

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sheratan_test_p (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 sheratan_test_p across your stack and pipelines.
If you installed it — respond
sheratan_test_p is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If sheratan_test_p 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 sheratan_test_p 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. sheratan_test_p 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

IN-MAL-2026-006877

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sheratan_test_p-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database