Which versions of upstart-offer-container are malicious?

Every published version of upstart-offer-container on npm is considered malicious. Remove the package entirely.

How do I remediate upstart-offer-container if I installed it?

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

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

Yes — upstart-offer-container is associated with the GHSA-232r-w3h2-2hv5 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 upstart-offer-container 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 upstart-offer-container (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upstart-offer-container across your stack and pipelines.

Malicious package

upstart-offer-containernpm

Malicious code in upstart-offer-container (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2613

Immediate action

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

npm uninstall upstart-offer-container

What this malware does

Package collects sensitive data (SSH keys, AWS creds, env vars), exfiltrates it to a remote server, and executes shell commands. MALWARE!

The package upstart-offer-container 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)

874e48e71ba19f19b7f284455c8f6a9c102828fa697926226ff59ef260fbc3af

148e48dd7b06a250063027a17895962000ca784a3fe52b704bea049afc85763a

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 upstart-offer-container (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging upstart-offer-container across your stack and pipelines.
If you installed it — respond
upstart-offer-container 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 upstart-offer-container 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 upstart-offer-container 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. upstart-offer-container 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-232r-w3h2-2hv5

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks upstart-offer-container-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