aws-blognpm
aws-blog is a confirmed malicious npm package (MAL-2026-15498) that executes malicious code on install (malicious versions 45.0.0, 45.0.1, 45.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in aws-blog (npm)
What this malware does
package.json declares a dependency whose key equals the package's own name (aws-blog) with a value of https://repo.securityctrl.com/aws-blog instead of a registry version range. On npm install, npm fetches whatever tarball bytes that URL currently returns and installs it, running any lifecycle scripts inside it. There is no version pin and no integrity hash, so the executed code is whatever the operator of repo.securityctrl.com serves at install time and can change silently between installs. The shipped source is an inert stub, so the manifest line is the entire published surface of the package. The dependency-confusion shape (self-named key, implausibly high 45.0.0 version to win resolution against an internal aws-blog, host unrelated to any AWS or npm infrastructure) further indicates targeting of installers who expect an internal package by this name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aws-blog (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aws-blog across your stack and pipelines.
If you installed it — respond
Remove aws-blog 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 aws-blog 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 aws-blog 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks aws-blog-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.