Which versions of upstartautoretailadmin are malicious?

Every published version of upstartautoretailadmin on npm is considered malicious. Remove the package entirely.

How do I remediate upstartautoretailadmin if I installed it?

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

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

Yes — upstartautoretailadmin is associated with the GHSA-5vc6-vrhq-w4h9 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 upstartautoretailadmin 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 upstartautoretailadmin (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upstartautoretailadmin across your stack and pipelines.

Malicious package

upstartautoretailadminnpm

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

MAL-2026-2617

Immediate action

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

npm uninstall upstartautoretailadmin

What this malware does

Package is malware. Collects sensitive info (SSH keys, AWS creds, bash history, system info), executes commands, & exfiltrates data to a remote server.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

7e2e75e1fc7c5d93987dc0cf2bb562ce91a47b25ccec3ec2e0403e81551d51cd

9edbed871d1889b053bc8348b33250ffc9a92979323ecb9133d379e2e3836c2d

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

Campaign

GHSA-5vc6-vrhq-w4h9

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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