Which versions of published_at are malicious?

The following npm versions of published_at are flagged malicious: 99.9.9, 99.9.10, 99.9.11. Treat any of these as compromised.

How do I remediate published_at if I installed it?

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

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

Yes — published_at is associated with the GHSA-8xrh-276g-pwhf, RLMA-2026-01516 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 published_at 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 published_at (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging published_at across your stack and pipelines.

Malicious package

published_atnpm

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

MAL-2026-43

Immediate action

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

npm uninstall published_at

What this malware does

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

3 flagged

99.9.999.9.1099.9.11

Indicators of compromise (SHA-256)

dcecd48f5e6fb3589ec38336393f753621839d5278f70c28e6349129fd2eb39b

e6089f817f79b6c53b35373aac18fd90de2fba2940ba8daa1286c5d82ede4a9c

2cb8b86ec7a52550ec6870fb6ccd4ac48569df35395148617a605dddb42e1378

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 published_at (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging published_at across your stack and pipelines.
If you installed it — respond
Remove published_at 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 published_at 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 published_at 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. published_at on npm has been identified as a malicious package (versions 99.9.9, 99.9.10, 99.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8xrh-276g-pwhfRLMA-2026-01516

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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