Which versions of autoshipment-public-front are malicious?

The following npm versions of autoshipment-public-front are flagged malicious: 99.99.0. Treat any of these as compromised.

How do I remediate autoshipment-public-front if I installed it?

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

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

Yes — autoshipment-public-front is associated with the GHSA-qrhg-p488-7f87 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 autoshipment-public-front 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 autoshipment-public-front (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging autoshipment-public-front across your stack and pipelines.

Malicious package

autoshipment-public-frontnpm

Malicious code in autoshipment-public-front (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2274

Immediate action

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

npm uninstall autoshipment-public-front

What this malware does

The package autoshipment-public-front 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.

The OpenSSF Package Analysis project identified 'autoshipment-public-front' @ 99.99.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.99.0

Indicators of compromise (SHA-256)

31ad2f0aff522d10bc2bc6806839dd9ba49f7e4d6866306ffa21ee34ae44de38

9e88d7d57a4db4ac2a1f359905f9bff3aba5176c373833890d1f58befc32b4d8

2e3f7367b43d34278505e216c92d5b9f6510320c1593c200077d1cabce8b9f1b

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

Campaign

GHSA-qrhg-p488-7f87

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks autoshipment-public-front-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