Which versions of yastatic-s3 are malicious?

The following npm versions of yastatic-s3 are flagged malicious: 0.1.0, 0.1.10, 0.1.99. Treat any of these as compromised.

How do I remediate yastatic-s3 if I installed it?

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

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

Yes — yastatic-s3 is associated with the IN-MAL-2026-007741, IN-MAL-2026-008287, IN-MAL-2026-008283 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 yastatic-s3 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 yastatic-s3 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging yastatic-s3 across your stack and pipelines.

Malicious package

yastatic-s3npm

yastatic-s3 is a confirmed malicious npm package (MAL-2026-6586) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.10, 0.1.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in yastatic-s3 (npm)

MAL-2026-6586

Immediate action

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

npm uninstall yastatic-s3

What this malware does

Package name mimics Yandex's yastatic static-asset namespace. On install, postinstall.js performs an unconditional plain-HTTP GET to a hardcoded bare-IP endpoint http://130.49.177.51:18080/p/dc-20260627-yandex-geobase with query parameters carrying only the package name, version, and a fixed nonce. No environment variables, filesystem contents, credentials, or host identifiers are read or transmitted, and no code is fetched or executed from the remote endpoint. The behavior is a namespace-squatting placeholder with an install-time execution beacon: it confirms to the operator of the bare-IP endpoint that a target environment misresolved the public name into a private dependency tree. Installing this package does not exfiltrate installer data or execute attacker-controlled code, but it does reveal internal install activity to a third-party endpoint and occupies a namespace that resembles a well-known vendor's.

Malicious versions

3 flagged

0.1.00.1.100.1.99

Indicators of compromise (SHA-256)

6b9f052f01ba026de50b8dd1c26ccb2fe661367414f9139676f94eccaa3b8c50

4ddbcc63dbf0c8589eb16f0bfbd355d36ded28afce717b17af7dc1ad002d43da

f6abc47a32b453ee0a12ea33e7512ccdea60ed1868839e952cbeedaccd002a06

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

Campaign

IN-MAL-2026-007741IN-MAL-2026-008287IN-MAL-2026-008283

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks yastatic-s3-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